Free rw software for linux

dvd+rw-tools project makes it possible to burn DVD images created by "dvdauthor" or "mkisofs" to DVD+R, DVD+RW, DVD-R, and DVD-RW disks, replacing "cdrecord-proDVD" in many cases.

The package contains "growisofs" to burn DVD images or create a data DVD on the fly, "dvd+rw-format" to format a DVD+RW, "dvd+rw-mediainfo" to give details about DVD disks, and some programs to control the write speed and obtain information from DVD-RAM.

The cryptoswap package supports building an encrypted swap partition when a system boots. This must be necessary on systems that use encrypted filesystems because plaintext secrets may be written to disk when memory is swapped to disk.
Cryptoswap.sh should be installed in /etc/init.d. During system boot, cryptoswap.sh should execute right before checkroot.sh. When shutting down, cryptoswap should execute after sysklogd.
This package also includes an initialization script for building loopback encrypted /tmp. This may be necessary if a system contains encrypted filesystems but / is not encrypted. A link from directories like /var/tmp to /tmp may be appropriate. There are a few other alternatives for systems such as these:
1. Tmpfs is a Linux kernel feature that allows /tmp to exist in memory. This is a good solution for systems with a lot of memory and/or (encrypted) swap.
2. If you have a system that uses encrypted home directories, per-user temporary directories inside $HOME could be used. This would ensure that users data is protected but would require that all applications use $HOME/tmp instead of /tmp.
Finally, the project may be used to create an encrypted root filesystem. Doing so requires two special partitions. First, create a small partition to hold your kernel and initrd image, /dev/hdaX. Second create a large partition to contain the root of your filesystem, /dev/hdaY.
Next configure and install an initrd-based boot system:
1. Ensure romfs is compiled in your kernel (not a module).
2. Create a kernel-supported filesystem on /dev/hdaX and copy your kernel to /vmlinux.
3. Download busybox and extract it as initrd/busybox.
4. Update initrd/src/etc/modules.initrd to include any modules needed to boot.
5. Build cryptoswaps initrd image (cd initrd && make initrd) and copy it to the filesystem on /dev/hdaX at /initrd.img.gz.
6. Make sure you use literal = "root=/dev/ram0 init=/linuxrc rw" or LILO equivalent.
Finally, create a proper encrypted filesystem on /dev/hdaY:
1. Randomize the partition: dd if=/dev/urandom of=/dev/hdaY.
2. Set up a loopback device: openssl enc -d -aes-256-ecb -in initrd/src/etc/efsk | losetup -p0 -e aes /dev/loop0 /dev/hdaY.
3. Create the root filesystem: mkfs.ext2 /dev/loop0.
4. Mount your new root filesystem: mount /dev/loop0 .
5. Populate your new root filesystem.
Enhancements:
- Added initrd build environment.
- Documentation update.

Cdw is an ncurses and GTK2 based CD burning frontend for cdrecord & mkisofs taht ca run on linux console and GNOME desktop.
Cdw is a CD burning front-end for Linux.
Main features:
- Burning data CDs
- Burning audio CDs
- Burning from iso image
- Burning direct without image
- Create iso image
- Copy image from exist data CD
- Direct CD copy
- Blank CD/RW
- Disk at once writing
- Writing Joliet and Rock Ridge format
- dic catalog support
- Dummy write

Basically, its an approach to build a small, cut to the bone, ready and easy to install VDR Linux distribution.
LinVDR is a complete, breathing Linux system smaller than 128 MB with a complete digital Video Disk Recorder (VDR) / Personal Video Recorder (PVR) and several plugins -- listed seperately below.
For easy access we installed additionaly the browser frontend VDR Admin and a Samba share for up- and downloading music or DVD images with Windows clients.
The base system is Debian Woody compatible (only compatible, not Debian Woody itself!) with the DVB driver from Convergence and Klaus Schmidingers unbeated Video Disk Recorder Software VDR.
All this Tom has mixed smoothly together, and I made the install system and installation programme -- suitable for normal users without Linux knowledge.
Enhancements:
VDR Version and Plugins
VDR 1.3.17 with enAIO-Patch and this plugins:
- Autotimer-Edit 0.1.4 new
- DVD-Burn 0.0.5 new
- Clock 0.0.5b1 update
- Console 0.6 update
- DVD 0.3.5b06 (without CSS support)
- EPG-Search 0.0.3 new
- Femon (signal strength) 0.1.6 update
- Games 0.6.1 update
- GraphLCD 0.1.1 update
- GraphTFT 0.0.8 new
- Hello 0.1.0
- Image (Diashow) 0.2.2 update
- LCD-Proc 0.0.10 update
- Mailbox 0.3 update
- Manual 0.0.2 (german only) new
- Media-MVP 0.1.5 new
- Media-MVP-Server new
- M-LCD 0.0.4 update
- MP3 0.9.8 update
- MPlayer 0.9.8 update
- OSD-Demo 0.1.0
- Osd-PiP Plugin 0.0.7 update
- OSD-Teletext 0.3.1 update
- Pilot 0.0.7 new
- PIM 0.0.3 new
- Remote 0.3.2 (for IR receiver of Hauppauge Nexus-s cards) update
- Skin-Curses 0.1.0
- Sky 0.1.1
- Sleeptimer 0.6 update
- Status 0.1.0
- Stream-Dev 0.3.3 update
- Taste 0.0.2b new
- Text2Skin (loadable skins) 0.0.8.1 new
- Timeline 0.8.1
- TV-OnScreen 0.6.0 update
- TVTV 0.1.6
- VBox (ISDN voice mailbox) 0.5.1 update
- (S)VCD 0.0.6c
- VDR-CD (playing audio CDs) 0.0.10 update
- WAP 0.0.6d new
Others
- Multi-Language support (currently German and English)
- Install programm updated
- Setup programm updated
- Kernel 2.6.9 with support for (nearly) all chipsets and network cards updated
- DVB driver CVS 2004-12-03 updated
- VDR Admin 0.97 supporting VDR 1.3.x updated
- MPlayer 1.0pre5
- NoAd 0.4.2
- FBTV updated
- Samba 3.0
- DVD-Author 0.6.10 updated
- convert.pl
- vdrsync
- Editor nano
- Alsa
- USB Keyboard support
- dvd+rw-tools 5.13.4.7.4 (suitable for DVD+R/W and DVD-R/W)
- udftools
- Read-only support for NTFS

herodot is a tool that parses the timeline of filesystem activity created by mactime and adds human readable descriptions to it (e.g.: this file has been created). It also understands that later changes of some MAC tags hide earlier changes.

Usage:

Use this tool like that:

$ ./herodot < timeline.txt > interpreted_timeline.txt

Examples:

When the output of mactime says:

Wed Jun 15 2005 17:21:24 1024 m.c d/drwxr-xr-x root root 293340 /lib/tls/i686
herodot will say:

Wed Jun 15 2005 17:21:24 1024 m.c d/drwxr-xr-x root root 293340 /lib/tls/i686 (m.c) (subdirectory or file created in this directory)

It is because herodot knows that changing of m and c time tags of some directory without changing its a time means that some subdirectory or file has been created in this directory.

When the output of mactime says:

Mon Nov 07 2005 21:11:18 5 m.c -/-rw-r--r-- 0 0 15 katalog/dir_1/dir_1_1/fil_2.txt
Mon Nov 07 2005 21:11:20 5 .a. -/-rw-r--r-- 0 0 15 katalog/dir_1/dir_1_1/fil_2.txt
herodot will say:

Mon Nov 07 2005 21:11:20 5 .a. -/-rw-r--r-- 0 0 15 katalog/dir_1/dir_1_1/fil_2.txt (.a.) (reading from this file)
Mon Nov 07 2005 21:11:18 5 m.c -/-rw-r--r-- 0 0 15 katalog/dir_1/dir_1_1/fil_2.txt (m?c) (this file created) (writing to this file)

As you can see, the lines in herodots output are in oposite order the newest events come the first. Ok, thats not so much important side effect. Th important thing is that if the a tag was changed in some moment, we can not be sure if it was changed or not before that moment so in every older event of that file the tag a will be marked as ? (quotation mark).

Birne project is a very simple frontend for cdrecord and mkisofs.

With Birne you can burn files, ISO images and music files (currently supported are WAV, MP3 and Ogg Vorbis) to CD-ROM and CD-RW. It is not very mature yet but works for the most common situations.

Because Birne is intended to be used by people with little technical knowledge, there are no advanced configuration options in the user interface. If you need to change the default recording device, you have to alter the source. But since Birne is written in Python, this should be easy to change by most people (variable "recording_device in cdburner.py).

Support for configuration files is planned so that preparing Birne for usage by ordinary users should be easy.

You can run Birne by unpacking the tarball and running the executable "birne" in the directory created by tar. There is a very simple installer script which helps to set up Birne for all users on your system.

NIKTARIX is a new Knoppix like Live CD for the ppc platform. NIKTARIX LiveCD was build from scratch using code from KNOPPIX and KANOTIX and almost only Debian Sarge binaries where used.
NIKTARIX atm contains among others:
- kernel 2.6.11, KDE 3.3.2, UNIONFS, Mozilla / Firefox, Openoffice, GIMP
- Small notes about NIKTARIX :
- Some features are missing either because they are not ready/ported yet, some of them are i386 specific and can not work on the ppc platform, and some others could not compile yet.
- At the moment only the english language strings are included. Other languages will follow when ppl have a need for them.
- Knoppix cheatcodes _can_ be used, just put them at the end of the line in the OF prompt.
- UNIONFS takes a while to load when booting, just be patient.
- UNIONFS means that you can work like if it was from hard disk while it is running from CD. You can for example install/remove .deb files
To boot it use from the OF the command :
boot cd niktarix root=/dev/ram rw init=linuxrc"

B::Graph is a Perl compiler backend to produce graphs of OP trees.

SYNOPSIS

perl -MO=Graph,-text prog.pl >graph.txt

perl -MO=Graph,-vcg prog.pl >graph.vcg
xvcg graph.vcg

perl -MO=Graph,-dot prog.pl | dot -Tps >graph.ps

This module is a backend to the perl compiler (B::*) which, instead of outputting bytecode or C based on perls compiled version of a program, writes descriptions in graph-description languages specifying graphs that show the programs structure. It currently generates descriptions for the VCG tool (http://www.cs.uni-sb.de/RW/users/sander/html/gsvcg1.html) and Dot (part of the graph visualization toolkit from AT&T: http://www.research.att.com/sw/tools/graphviz/). It also can produce plain text output (which is more useful for debugging the module itself than anything else, though you might be able to make cut the nodes out and make a mobile or something similar).

OPTIONS

Like any other compiler backend, this module needs to be invoked using the O module to run correctly:

perl -MO=Graph,-opt,-opt,-opt program.pl
OR
perl -MO=Graph,-opt,obj -e BEGIN {$obj = ["hi"]}; print $obj
OR EVEN
perl -e use O qw(Graph -opt obj obj); print "hi!n";

Obj is the name of a perl variable whose contents will be examined. It cant be a my() variable, and it shouldnt have a prefix symbol ($@^*), though you can specify a package -- the name will be used to look up a GV, whose various fields will lead to the scalar, array, and other values that correspond to the named variable. If no object is specified, the whole main program, including the CV that points to its pad, will be displayed.

Each of the the opts can come from one of the following (each set is mutually exclusive; case and underscores are insignificant):

-text, -vcg, -dot

Produce output of the appropriate type. The default is -text, which isnt useful for much of anything (it does draw some nice ASCII boxes, though).

-addrs, -no_addrs

Each of the nodes on the graph produced corresponds to a C structure that has an address and includes pointers to other structures. The module uses these addresses to decide how to draw edges, but it makes the graph more compact if they arent printed. The default is -no_addrs.

-compile_order, -run_order

The collection of OPs that perl compiles a script into has two different layers of structure. It has a tree structure which corresponds roughly to the synactic nesting of constructs in the source text, and a roughly linked-list representation, essentially a postorder traversal of this tree, which is used at runtime to decide what to do next. The graph can be drawn to emphasize one structure or the other. The former, compile_order, is the default, as it tends to lead to graphs with aspect ratios close to those of standard paper.

-SVs, -no_SVs

If OPs represent a programs compiled code, SVs represent its data. This includes literal numbers and strings (IVs, NVs, PVs, PVIVs, and PVNVs), regular arrays, hashes, and references (AVs, HVs, and RVs), but also the structures that correspond to individual variables (special HVs for symbol tables and GVs to represent values within them, and special AVs that hold my() variables (as well as compiler temporaries)), structures that keep track of code (CVs), and a variety of others. The default is to display all these too, to give a complete picture, but if you arent in a holistic mood, you can make them disappear.

-ellipses, -rhombs

The module tries to give the nodes representing SVs a different shape from those of OPs. OPs are usually rectangular, so two obvious shapes for SVs are ellipses and rhombuses (stretched diamonds). This option currently only makes a difference for VCG (ellipse is the default).

-stashes, -no_stashes

The hashes that perl uses to represent symbol tables are called stashes. Since every GV has a pointer back to its stash, its virtually inevitable for the links in a graph to lead to the main stash. Unfortunately stashes, especially the main one, can be quite big, and lead to forests of other structures -- theres one GV and another SV for each magic variable, plus all of @INC and %ENV, and so on. To prevent information overload, then, the display of stashes is disabled by default.

-fileGVs, -no_fileGVs

Another kind graph element that can be annoying are the pointers from every GV and COP (a kind of OP that occurs for every statement) to the GV that represents the file from which that code came (used for error messages). By default, these links arent shown, to keep them from cluttering the graph. Also, perls internal interfaces changed in a recent version, so in perl 5.005_63 or later you cant see the fileGVs at all.

-SEQs, -no_SEQs

As it is visited in the peephole optimization phase, each OP gets a sequence number, which is currently used by anything (except the peephole optimizer, to avoid visiting OPs twice). If you want to see these, ask for them. (COPs have their own sequence numbers too, but theyre more interesting to look at -- for instance, theyre used to bound the lifetimes of lexicals).

-types, -no_types

B::Graph always gives the type of each OP symbolically (entersub), but it can also print the numeric value of the type field, if you want. The default is no_types.

-float, -no_float

Almost every OP has an op_next and an op_sibling pointer, and B::Graph colors them distinctively (pink and light blue, respectively). Because of this, it isnt strictly necessary to anchor the arrow on a line in the OPs box saying op_next. The float option lets the graph layout engine start these arrows wherever it wants, which can sometimes lead to a more pleasing layout, at the expense of being less obvious. The default is not to float.

-targlinks, -no_targlinks

Lexical (my()) variables and temporary values used by individual OPs are stored in pads, per-code arrays linked to the CV. OPs store indexes into these arrays in the op_targ field, but B::Graph can often also draw links directly from the OP to the SV that stores the name of the variable. These links dont correspond to any real pointers, however, and they can make the graph more complicated, so they are disabled by default.