Free hd software for linux

wmhdplop project monitors your hard drives and displays visual information about their activity (read, write, swapin, swapout), and optionally (if hddtemp is running as a daemon), displays their temperature/status.
Main features:
- 0-portability, wont compile/run on anything without a recent kernel (see requirements below)
- useless animation reflecting disc I/O.
- another useless animation reflecting swap activity.
- annoying blinking leds.
- a textual information of your harddrive throughput.
- supports ide drives, and (not 100% sure) scsi and md arrays.
- display of the hd temperature if the hddtemp daemon is running.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package.
It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

DecryptHD software can be used for realtime HD DVD decryption while streaming the decrypted movie to the player. It uses drive authentication to obtain the volume ID from it. This means it doesnt use a key database, but you do need a real drive. Without a real drive theres probably no point in realtime decryption anyway. Not wanting to watch all files on disc starting from A to Z, this also means it works on a per file basis. You have to specify the file you want to watch.

At the moment, this tool is Linux only for the simple reason that its my normal desktop and development environment (Debian). So its kinda obvious the targeted player is mplayer because of this. This is also where the streaming comes into the picture. The ffvc1 decoder not only works for normal playback from harddisk, but also supports streaming.

The current status of the tool is that it works and runs stable. But Ive only tested it with the Bourne Supremacy, but Im hoping that it should with all HD DVDs released to date. Mind the "hoping" though since a 1 disc test is not a 100% guarantee. See this as a testrun. Its written in C++ and if theres demand Ill release the source once the rough edges are gone. Also need to improve the subset-difference stuff first, its kinda sucky the way its implemented right now. Also both currently discovered processing keys are in it (lets get this into the open right away). The advantage of this is that theres no fiddling with keys, but the downside is that when keys get revoked/discovered, this will require an update of the app. Maybe Ill make a different solution at a later time, who knows.

If you run into trouble (so many things can go wrong), theres a log created called decrypthd.log in the same directory the tool is in. Please include it in any bug reports.

How to run:

1. unrar e decrypthd.rar (extracts the archive)
2. chmod +x decrypthd (makes it executable)
3. ./decrypthd (run the executable file)

Usage: decrypthd < device > < mountpoint > < filename > -o [options] | < player >

Options:

-c Chunksize

Example: decrypthd /dev/scd0 /mnt/hddvd/ file.evo -o | mplayer -demuxer mpegps -vc -ffvc1 -

First you need to plug in your drive if you havent done so already. Ive been using a Xbox360 HD DVD drive. Unmodified, just as you buy it in a store. Once plugged in youll need to find its device. Usually this is /dev/sr0 (its alias is /dev/scd0). This is the < device > value and you need this for the drive authentication. Next mount the drive (the < mountpoint >). In short now youre good to go.

In reality however, you need to know the filename of the evo you want to watch. On the disc Ive got here this is FEATURE_1.EVO (case sensitive). So look this up in the HVDVD_TS directory.

It uses OpenSSL for the signature calculations, so make sure youve got that.

Now fire the entire thing up (Im assuming youve got the latest mplayer). You need to specify the demuxer and decoder:

decrypthd /dev/scd0 /mnt/hddvd/ FEATURE_1.EVO -o | mplayer -demuxer mpegps -vc ffvc1 -

sdparm utility outputs and in some cases modifies SCSI device parameters. When the SCSI device is a disk, sdparms role is similar to its namesake: the Linux hdparm utility which is for ATA disks that usually have device names starting with "hd".
More generally sdparm can be used to output and modify parameters on any device that uses a SCSI command set. Apart from SCSI disks, such devices include CD/DVD drives (irrespective of transport), SCSI and ATAPI tape drives and SCSI enclosures. A small set of commands associated with starting and stopping the media, loading and unloading removable media and some other housekeeping functions can also be sent with this utility.
This utility currently contains over 500 entries spread across generic mode pages, transport specific mode pages, vendor specific mode pages, Vital Product Data (VPD) pages and their attributes. Rather than try and document all of these here (or in the man page), another approach is taken. This utilitys internal tables can be searched and output with the --enumerate option. Additional explanatory information is output when the --long option is used (and more if the --long option is used twice).
SCSI mode pages
Mode pages hold meta data about a SCSI device which can, in some cases, be changed by the user. In SCSI parlance the "device" is a logical unit of which there may be several in a SCSI target. In the case of a SCSI disk connected directly to a Host Bus Adapter (HBA) the disk is both a SCSI target and a logical unit. The "user" in this case is the person using sdparm which is a SCSI "application client" and it feeds commands into a SCSI initiator. The SCSI initiator is found in the HBA. At the command level SCSI is a client-server protocol with the logical unit (or target device) being the server that responds to commands sent by the application client via the SCSI initiator.
Mode pages are defined in SCSI (draft) standards found at www.t10.org . Mode pages common to all SCSI devices are found in the SCSI Primary Commands document (SPC-4) while those specific to block devices (e.g. disks) are found in SBC-3 and those for CD/DVD drives are found in MMC-5. This diagram shows how various SCSI and associated standards interrelate. Often device product manuals detail precisely which mode pages (and parts thereof) are supported by a particular model and describe the way that the device will react if the generic description in the SCSI (draft) standard needs amplification. There are also transport protocol specific mode pages for transports such as "spi" (the 25 year old SCSI Parallel Interface), "fcp" (Fibre Channel Protocol) and "sas" (Serial Attached SCSI). There are also vendor specific mode pages. Mode pages that are not transport protocol specific or vendor specific are sometimes referred to as "generic" in sdparms documentation.
To see a list of generic mode page names that sdparm has some information about use: sdparm -e. To see a list of transport specific mode page names that sdparm has some information about use (for example) sdparm -e -t sas. Both lists are sorted alphabetically by mode page abbreviation.
Mode pages are not the only mechanism in SCSI devices for holding meta data. Information which seldom if ever changes for a particular device may be found in the Vital Product Data (VPD) pages which are obtained via the SCSI INQUIRY command. Performance statistics are held in log pages which are obtained via the SCSI LOG SENSE command. Recent CD/DVD drives hold a lot of information in feature and profile descriptors (see MMC-4 and MMC-5) which are accessed via the SCSI GET CONFIGURATION command (see the sg_get_config utility in the sg3_utils package).
Each mode page has up to four tables associated with it. These can be thought of like tabs on a spreadsheet, with each tab containing the same size table. The four tables are:
current values: those values that are active at this time
changeable values: bit masks showing those values that the user may change
default values: the manufacturers default values
saved values: those values that will be active after the next power cycle (or format)
The saved values are optional. If the mask in the changeable values indicates a field can be changed then the corresponding field in the current values may be changed. A bit of 0 in the changeable values mask indicates the corresponding bit in the current values (and saved values) may not be changed. A bit of 1 in the changeable values mask indicates the corresponding bit in the current values (and saved values) may be changed. At the point when a current value is changed, the user may also choose to change the corresponding saved value.
The manufacturer obviously knows a lot about the characteristics of its devices. Hence if a current field value (and saved field value) is different from the default field value then there should be some rationale.
Some current values represent a state within the target device or logical unit. If that state changes so does the current value. Such values are not usually changeable by the user.
The sdparm utility has a --get, --set, --clear type of command line interface in which mode page fields are identified by an acronym. In many cases these acronyms will correspond precisely to the standard (e.g. "WCE" for Writeback Cache Enable in the caching mode page of SBC-3). For some longer fields the standards "spell out" a field name (e.g. "Write Retention Priority" in the caching mode page of SBC-3). In such cases the sdparm utility uses an acronym (e.g. "WRP"). In sdparm, acronyms across all generic mode pages are unique (i.e. an acronym matches at most one field of one generic mode page). Each transport protocol has its own namespace of acronyms so that an acronym is unique within a transport protocol. By default, saved values are not changed by --set and --clear. When changing the current values, the saved values can be changed as well by adding the --save. All the current values in a mode page can be changed back to the manufacturers defaults with the --defaults option (and the --save option here will additionally change the saved values back to the manufacturers defaults).
Changing some mode page fields is like jumping off a cliff holding onto a rope which you are not sure is properly secured. If in doubt, change the current value without using the --save option. That way if the setting is disastrous, power cycling the device will restore the previous setting. Once the new setting is known to be safe, then the sdparm utility can be re-executed with the --save option added.
sdparm commands
The --command= option allows a command to be sent to the given device. The currently supported commands are:
capacity: sends a READ CAPACITY and if successful reports the number of blocks, block length and capacity expressed in MibiBytes (1048576 bytes). Valid for disks and CD/DVD drives with the appropriate media loaded.
eject: stops the medium (if it is spinning) and ejects it from the drive. Note that this may be prevented by software in which case use the unlock command first.
load: loads the medium and then spins it up
ready: reports whether the medium is ready for IO. Ready usually means that it is present and spun up. If the device is not ready then the exit status will be 2 (see exit status section below).
sense: reports sense data (from a REQUEST SENSE SCSI command); can include power condition information, a progress indication for a time consuming command (e.g. format) or a report an informational exception (when MRIE=6)
start: spin up the medium
stop: spin down the medium
sync: send a SYNCHRONIZE CACHE SCSI command to the device.
unlock: instructs the device to allow medium removal (i.e. an eject). Beware, the OS may have had a good reason for preventing removal of the medium (e.g. it contains a mounted file system). Use at your own risk.
These sdparm commands send SCSI commands to the given DEVICE. If they dont seem to work, adding a verbose flag (i.e. -v or -vv) may provide more information. The "ready" and "sense" commands need read permissions on the DEVICE while the other commands need both read and write permissions.
Enhancements:
- Changes to SCSI mode and VPD pages that were introduced by t10.org since the last release were incorporated.
- The pass-through interface was updated, and code which is written in C was made to compile cleanly with C++.

SchilliX is an OpenSolaris based distribution which runs from CD and could be installed on your harddisk or onto an USB memory stick.
Main features:
Highlights:
- In 30sec fron bootmanager to multiuser login prompt (HD-boot)
- Booting from CD or USB-Stick.
- Installs to your harddisk
- Self healing Services
Software:
- cdrecord
- star
- bash
- bz2
- fakeroot
- gmake
- gpatch
- gtar
- gzip
- pod2man
- texinfo
- unzip
- wget
- gcc-3.4.3
- all Schilly tools
- smake as /usr/ccs/bin/make
- ... more to come
Enhancements:
- Updated to use OpenSolaris Nevada Build 36.
- An SVr4 package database for the content was added (although the build process is not yet based on pkgadd).
- This allows you to install most binary packages from Blastwave.org.
- The DHCP eventhook can deal with multiple DHCP networks on multiple interfaces.

Dreamlinux distribution is a modern and modular Linux system that can be run directly from the CD and optionally be easily installed onto your HD.
Dreamlinux comes with a selection of the best applications designed to meet mostly of your daily needs.
Dreamlinux is based on Debian and Morphix, which means it takes advantages of their best features and adds its own modern development tools.
Being a modular system Dreamlinux allows you to add new modules comprising your preferred applications and build a new Distro that meet your requirements by means of its revolutionary MKDistro tool.
Enhancements:
- The final version of Dreamlinux 2.2 Multimedia Edition has been released. Having many improvements compared with the previous version, Dreamlinux 2.2 Multimedia Edition brings countless new features. The kernel is 2.6.18, and the distro uses Debian testing repositories. A greater number of applications for multimedia have been added, allowing to open and manipulate many different types of audio and video files. Beyond the many updates, other refinements have also been incorporated: upgrade assistant, new control panel, and the Easy-Install application that allows the user to install non-Debian programs like Google Earth, Picasa, Opera, etc.

Date::Hijri is a Perl extension to convert islamic (hijri) and gregorian dates.

SYNOPSIS

use Date::Hijri;

# convert gregorian to hijri date
my ($hd, $hm, $hy) = g2h($gd, $gm, $gy);

# convert hijri to gregorian date
my ($gd, $gm, $gy) = h2g($hd, $hm, $hy);

This simple module converts gregorian dates to islamic (hijri) and vice versa.
The dates must be given as an array containing the day, month and year, and return the corresponding date as a list with the same elements.

Archie project is a complete live Arch linux system (v0.7) to be run from a cd/usb, built with the KISS philosophy in mind. No packages have been stripped to provide a full Arch linux system, yet deliver fastest performance with no extensive bloating.
Archie uses its own hw-detection tool (lshwd) ideally to support a wide range of hardware with low detection time. Archie also provides extended features like multi-lingual, nesting capabilities and hd-install.
Main features:
- KISS
- Performance, performance, performance
- Unique hw-detection tool (lshwd)
- Automatic desktop/optional startup dialogs
- nesting root (/) or home (/home) directories
- hd-install