Free trim software for linux

Trim 1.0 is an effective utility for monitoring and controling the sizes of (log) files. Examines a text file to see if its length has exceeded a certain limit; if it has, Trim removes a certain number of lines from the beginning of the file. Ideal for use in crontab.

crip is a terminal-based ripper/encoder/tagger tool for creating Ogg Vorbis/FLAC/MP3 files under UNIX/Linux. It is well-suited for anyone (especially the perfectionist) who seeks to make a lot of files from CDs and have them all properly labeled and professional-quality with a minimum of hassle and yet still have flexibility and full control over everything. Current versions of crip only support Ogg Vorbis and FLAC. If you want to encode MP3 files you should use crip-1.0.
I am constantly refining the process of creating perfect music files to be as automated as possible while still leaving the user with control over as much as possible. To see for yourself how painless it is to make professional-grade music files on your UNIX/Linux machine, go through the crip tutorial.
This script is special because it is the only one that I know that is capable of doing group vorbisgain/replaygain and/or normalization (adjust the volume to be as loud as possible without clipping/distortion) and group labelling/tagging, which makes it easy to allow a group of tracks to be treated as one piece. It can also trim off the silence at the beginning and end of these tracks/groups.
First the script fetches the CDDB info off the internet. Then it prompts you for the grouping of the tracks. This is important because it will treat each group of tracks as one piece, label and vorbisgain/replaygain and/or normalize them (using the volume gain/peak of that group). Normalization is now obsolete with the creation of vorbisgain (replaygain) utilities, so I have that turned off by default and itll run vorbisgain instead.
You can, of course, have each track be a group by itself (such as what youd want to do with most pop CDs). But since Ive also ripped a lot of Classical music I found it necessary to group tracks differently fairly often.
Then it will prompt you for the Artist and Album info (which is already defaulted to what is pulled from CDDB). Afterwards it will prompt you for a filename for each track you selected. Again this field is defaulted to what it suspects that youd want. For most pop CDs all I have to do is hit enter here because the filename is almost always exactly what Id want.
It will then prompt you that its ready to rip. From here everything is automated, so hit return and it usually finishes in about an hour. The script calls cdparanoia to rip the tracks, and then oggenc/flac/lame to encode them. It also labels the files with info appropriately, including the CDDB CD DiscID number (so you will always have a CD reference hex-number inside your OGG/FLAC/MP3 file).
Ive looked into other scripts out there that do something similar to this script, but decided to write my own since I couldnt find one that groups tracks and trims silence. I used this script to rip and encode my collection of over 200 Bach CDs, as well as a bunch of other Classical and non-Classical CDs very easily.
Ive provided links below that include some of the prerequisites that you may need.
Main features:
- Track grouping for automated tagging and appropriate normalization/vorbisgain on multi-track pieces.
- CDDB fetching to populate default information.
- CDDB submit to update the CDDB database with your more accurate info.
- Automates as much of the tagging as possible for fully-labeled professional quality music files.
- Automatically trims digital silence at the beginning and end of a track/group (if desired).
- European character support. Also European character-mapping support.
- Flexibility and full user control in tagging and file naming.
Enhancements:
- Bugfix: -m flag on the command line was not being processed

PostScript::MailLabels are modules for creating PostScript files of mailing address labels.
Flexible enough to tackle other printing tasks, basically anything requiring a set fields be printed on a regular grid. Also creates PostScript(tm) code for calibrating and testing mailing label printing.
The module has three distinct output modes. In my experience, printing mailing labels is a matter of tweaking parameters to get them all to fit properly on the page. This module is designed with this in mind.
The first output is the calibration sheet. This is a pair of annotated axes, either in inches or centimeters, centered on the page and covering the whole page in X and Y directions. The intent is for you to output this page first, and simply read off the relevant page dimensions directly.
The second output is the label test. This output is a series of boxes drawn on the page, meant to outline the edges of all the mailing labels. Take this sheet and line it up with a sheet of labels to see if they actually match perfectly. If not, tweak the parameters until they do. Note that sometimes you will get a message at the bottom of the sheet saying ``Bottom gap too large, last row cannot be printed.
This means that the printable area of your printer is too small to utilize the last row of labels. I have this problem. But I handle it for you. Note also the arrows on the test sheet. As you hold the test sheet over a sheet of labels, hold it up to the light and slide the test sheet so that the boxes match the edges of the labels. If you slide in the arrow direction, that is a positive adjustment.
The other direction is negative. If the edges of some boxes come out dashed, that means that the non-printing border cuts off the end of the label, so I will adjust the printing area appropriately. Dont try to line up the dashed lines with label edges - it wont work. Just line up the solid lines.
The third output is the labels themselves. By default, I have set up a US-centric address definition :
firstname, lastname, street address, city, state, zipcode
But with version 2.0, you can now create your own definition. You can define new fields, and you can define how those fields land on a label. You can also control the fonts on a per-field basis. Not the size, yet - later pilgrim.
Parameters you can set :
Paper size, orientation, borders on the printable area (many printers will not print right up to the edge of the paper), where the labels live on the page and how big they are, overall x-y shift of page, whether or not to print PostNET barcode, font, fontsize, units (english or metric), which Avery(tm) product code to use, and where the first label starts.
This last needs explanation. If you have a partially used sheet of labels, you might want to use it up. So you count the missing labels, starting at the upper left, and counting across, and then down. For example, if I have 3 columns of labels, label five is the second label in the second row.
If you have an Avery(tm) product that I havent defined, send me the specs and Ill add it.
Also, if there is another brand of labels that you use, send me the relevant data and Ill add that as well. I suspect that there must be some other vendor in Europe, but I dont know who that would be.
When setting up the addresses, I check to see if they will fit on the label. If not, I try to shorten them semi-intelligently until they fit. This part could use quite a bit more work, if done right it probably merits a module all its own.
Briefly, for the name line, I start trimming the ends off the first name, and leave the last name alone.
For the street, I look for things like Road or Avenue and nuke those first, then I trim the street name from the right.
Enhancements:
- Parentheses are now escaped in the generated PostScript code.

TextSort application allows you to sort the lines of a text alphabetically.
This program is released under the GPL license.
Main features:
- Case sensitive or insensitive
- Trim lines, remove empty lines
- Remove duplicates

Ubuntu Lites idea is to bring the power of Ubuntu across to the users of Legacy systems. So not just to make a small linux as this has been done before (Puppy Linux, Damn Small linux, the Rule Project). Nor to make a useable linux based desktop Operating system (that has been done with Ubuntu Linux, Beatrix).

The idea is to bring the power of Ubuntu to the typical users of Legacy hardware (ie the grandma who gets an old P2 set up for her but does not know how to use it).

So to this end the Operating system needs to be:

* Easily used by people with minimal computer skills
* Useable on a resurected system (see system specifications below)
* and is able to satisfy a typical users requirement of Applications and functionality.

These are the three core aims of the Ubuntu Lite Project.

We will also provide development guides to anyone who wants to trim down their versions or help others use linux on reconditioned hardware. I hope that you enjoy Ubuntu Lite and that you find it useful.

Devel::STrace::Monitor is a monitor interface component for Devel::STrace.

SYNOPSIS

#
# open the mmaped file
#
use Devel::STrace::Monitor;

my $view = Devel::STrace::Monitor->open(somefile.map);

my $cycles = 0;
while (1) {
print "n**************************************n";
#
# refresh the internal ringbuffer map
#
$view->refresh();
#
# dump the current traces
#
$view->trace(&dump_trace);

sleep 10;
}
#
# method to display the traces
#
sub dump_trace {
my ($key, $slot, $depth, $line, $time, $entry) = @_;

$lastkey = $key,
print "n**************************************n"
unless ($lastkey eq $key);

if ($time) {
#
# trim the weekday and year from timestamp
#
my $frac = ($time - int($time)) * 1000000;
$frac=~s/..*$//;
my @parts = split(/s+/, scalar localtime($time));
pop @parts; # get rid of year
print "$key($depth) : $slot : $entry:$line at ",
join( , @parts), ., $frac, "n";
}
else {
print "$key($depth) : $slot : $entry:$line (No timestamp)n";
}
}

Provides methods to attach to and read the memory mapped file generated by Devel::STrace (or future full featured debuggers) using Devel::RingBuffer.

set or clear any of the $DB::single, $DB::trace, or $DB::signal control variables of the AUT (via their tied interfaces in the AUT).

inspect the current execution call stack of the AUT

The interfaces provide a simple framework for building an external application that can attach to a running Perl application, monitor its current execution, and eventually detach, all while permitting the application continue to run uninterrupted.

A more complete debugger module is planned to exploit the various command/control structures available via Devel::RingBuffer. Note that this module will be fully compatible with the resulting debugger so that, e.g., an application can first be monitored to detect troublespots, and then the debugger can be attached to fully debug the problem.

CRUX is a lightweight, i686-optimized Linux distribution targeted at experienced Linux users.
The primary focus of this distribution is "keep it simple", which is reflected in a simple tar.gz-based package system, BSD-style initscripts, and a relatively small collection of trimmed packages.
The secondary focus is utilization of new Linux features and recent tools and libraries. CRUX also has a ports system which makes it easy to install and upgrade applications.
There are many Linux distributions out there these days, so what makes this distribution any better than the others? Well, its all about taste really. I can give you a hint about my taste, and perhaps we share the same taste, or we dont.
First of all, I want a distribution made with simplicity in mind from beginning to end. Further, I want my packages up-to-date, not the latest bleeding-edge-alpha version, but the latest stable version. I want to easily create new and update old packages (updating a package in CRUX is often just a matter of typing pkgmk -d -u).
I want packages optimized for my processor (think -march=i686). I dont want my filesystem cluttered with files I never use (think /usr/doc/*, etc). If I need more information about a specific program, other than information found on the man-page, Ill find it on the net. And finally, I want to use new features offered by recent Linux kernels (think devfs, reiserfs, ext3fs, etc).
If you are a somewhat experienced Linux user that wants a clean and solid Linux distribution as the foundation of your installation, prefers editing configuration files with an editor to using a GUI, and doesnt hesitate to download and compile programs yourself, then this distribution might suit you well.
Enhancements:
- CRUX 2.3 has been released." Whats new? "CRUX 2.3 includes glibc 2.5 and GCC 4.1.2; the monolithic x11 package has been replaced by the new modular X.Org distribution - as the results of this update, crux.nu now hosts a dedicated xorg ports repository, installed by default; the netkit-base port has been replaced by inetd and iana-etc; by popular request we included iproute2 and iputils in the core collection.

gID3 is a GUI ID3 tag editor with a very nice user interface. It displays a list of all the files in a directory with the tag information, making it very easy to use. gID3 has a very nice user interface. Unlike other GUI id3 tag editors, gID3 displays a list of all the files in a directory with the tag info of each tag in one list making it very easy to use.
My goal is to make it the most usefull ID3 tag editor. I usually only make changes when I get feedback. So use it and give me some feedback.
MAKING:
type make
i havent tesed this on any machine except my linux box, but it should compile on any thing thats posix compliednt and has gnome properly installed.
INSTALLATION:
copy the binary file derived from making to /usr/local/bin or something like that.
Enhancements:
- fixed limit/boundary checks in the trim() function, which caused the worst segmentation faults;
- variable "recursive" initialized, which fixes other problems;
- code that changes "/" chars to spaces, since its a forbidden char for unix filesystems;
- the trim() function now uses isspace() instead of checking for spaces only, for the sake of completeness;
- remember the old dirname when the user selects .. in dirlist