Free mystery case files software for linux

The Plastic File System project is an LD_PRELOAD module for manipulating what the file system looks like for programs. This allows virtual file systems to exist in user space, without kernel hacks or modules.
PlasticFS includes the following file systems:
chroot
The chroot filter may be used to simulate the effects of the chroot(2) system call, in combination with other filters.
dos
The dos filter may be used to simulate an 8.3 DOS file system.
log
The log filter may be used to transparently log file system access, similar to the strace command.
shortname
The shortname filter may be used to simulate file systems with shorter filenames.
smartlink
The smartlink filter may be used to expand environment variables in symbolic links, using the usual $name notation.
upcase, downcase, titlecase and nocase
The upcase filter to make file names appear to be in upper-case when listed. File names are case- insensitive when being opened, etc. The downcase filetr is similar, except it converts to lower-case, titlecase capitalizes, and nocase is simply case insensitive without altering the filenames.
viewpath
The viewpath filter may be used to make a set of directory trees look like a single directory tree. (Also known as a union file system.) All modifications take place in the first directory in the list.
Aka: union and translucent
Note: Filters may be piped from one to the next, forming powerful combinations.
PlasticFS is currently dependent on the implementation of the GNU C Library. It is self configuring using a GNU Autoconf generated configure script.
Enhancements:
- Build problem fixed.

Kumula Cases is a case management software for lawyers (similar to programs like Amicus Attorney or RA-Micro), based upon the Kumula package. It was part of my diploma thesis and consists of multiple parts:

Cases:

The main application for handling the case files. It shows active and closed case files, and also the appointments and time limits of all cases. When opening a case file, it starts "CaseData", which is merely an "internal" application.

CaseData

Displays the content of one case file. Because of splitting the case management and the case contents, its possible to:

- work with different cases at the same time
- open a case from Cases and Clients (see below)
- open a case directly from your desktop (if you create a shortcut there)
This case content program is also modular and brings the following modules with it:
- Header, for storing reference number, case title etc.
- Parties, for managing clients, contrahents and third parties
- Events, for recording appointments, time limits and resubmissions
- Documents, for assigning letters and other documents to a case file
- Journal, for register revenues and expenses related to a case

Cases module for Clients

This module for Kumulas client management program shows the cases in which a client is involved, including the possibility to open the case file directly.

Non-Networked File System provides a consistent file system over several non networked UNIX computers (or slow networked). For example on your computer at home and at work using only a floppy disk for the synchronisation.
Main features:
- You are sure to work on the latest version of files.
- You dont need to remember which files are modified on an host and must be transfered on others.
- You dont need to made backup, because if a computer crash the file system is still on the other computers working with NNFS.
- The NNFS medium is choosen by a user shell script, it could be: floppy disk, usb key, serial connection, ...
- Minimal NNFS medium bandwidth to make the updates.
- EASY TO USE: Running ``nnfs command before and after your work.
- Numbered backup of files modified/deleted on NNFS.
- If you modify the same file on several hosts NNFS solves the update conflict.
- The program has been hugely tested.
Enhancements:
- This release fixes the case where the user modifies a file mode while NNFS is running and NNFS is configured in order that a file mode change does not imply file synchronization.

CLASS HIERARCHY

Hash::Case
is a Tie::StdHash
is a Tie::Hash

SYNOPSIS

use Hash::Case::Lower;
tie my(%lchash), Hash::Case::Lower;
$lchash{StraNGeKeY} = 3;
print keys %lchash; # strangekey

Hash::Case is the base class for various classes which tie special treatment for the casing of keys. Be aware of the differences in implementation: Lower and Upper are tied native hashes: these hashes have no need for hidden fields or other assisting data structured. A case Preserve hash will actually create three hashes.

The following strategies are implemented:

Hash::Case::Lower (native hash)

Keys are always considered lower case. The internals of this module translate any incoming key to lower case before it is used.

Hash::Case::Upper (native hash)

Like the ::Lower, but then all keys are always translated into upper case. This module can be of use for some databases, which do translate everything to capitals as well. To avoid confusion, you may want to have you own internal Perl hash do this as well.

Hash::Case::Preserve

The actual casing is ignored, but not forgotten.

METHODS

tie HASH, TIE, [VALUES,] OPTIONS

Tie the HASH with the TIE package which extends Hash::Case. The OPTIONS differ per implementation: read the manual page for the package you actually use. The VALUES is a reference to an array containing key-value pairs, or a reference to a hash: they fill the initial hash.

Examples:

my %x;
tie %x, Hash::Case::Lower;
$x{Upper} = 3;
print keys %x; # upper

my @y = (ABC => 3, DeF => 4);
tie %x, Hash::Case::Lower, @y;
print keys %x; # abc def

my %z = (ABC => 3, DeF => 4);
tie %x, Hash::Case::Lower, %z;
addPairs PAIRS

Specify an even length list of alternating key and value to be stored in the hash.

addHashData HASH

Add the data of a hash (passed as reference) to the created tied hash. The existing values in the hash remain, the keys are adapted to the needs of the the casing.

setHash HASH

The functionality differs for native and wrapper hashes. For native hashes, this is the same as first clearing the hash, and then a call to addHashData. Wrapper hashes will use the hash you specify here to store the data, and re-create the mapping hash.

Legal Case Management System is a software aimed for use by not-for-profit legal advice centres in order to make better follow-ups of their cases, including client consultations and court events.
Integration into your offices activities
The software can be installed either on one computer or shared over a network. You can then provide a personal access to each member of your organisation. This allows them to chose how they want to work on a case and how the case information should be shared with the other members.
Users can then create new cases (or campaigns) to which they can attach a list of people or organisations involved as well as to add follow-up information.
- Organisations providing advice or consultations will benefit from being able to quickly consult the database for background information on a clients case and evolution, contact information, etc.
- Lawyers can use the software to track the evolution of a case and the resources spent on a particular client, as well as to track the status of a case in court.
- Office managers can generate reports based on the activity for a given period. The variety of reports include: activity overview for each staff members, statistical information on cases or clients, and general overview on how the usage of the organisations resources. Such reports facilitate the reporting on projects and the creation of new budgets.
Software freedom
LCM is a Bulgarian community initiative developed by IRBF, funded by the Open Society Institute and distributed as "free software". The software is being developed for local not-for-profit advice centers, but anyone has the freedom to use it, to redistribute it locally and to adapt it to their own needs.
The software is currently available in English and Bulgarian, but more translations are welcomed and very easy to do with the help of an online translation interface.
Enhancements:
- This release fixes the "sum billed" format error (if the field is active), as well as the "case notes" being lost after edit.

Testitool is an application written in PHP that allows its users to compose and manage QA test plans.
Main features:
Test Plan Management
- Use Testitool to compose rich test plans containing an unlimited number of test cases. Each test case can be mapped to a functional requirement (documented elsewhere), can be assigned a type (e.g. regression, functional, etc.), and more.
Manage Individual Instances of Each Test Plan
- Each test plan contains the master list of all test cases for a given product. However, for any given release you may not want to execute each and every test case. Testitool allows you to pick and choose which test case you will want to execute for any given instance of the test plan. Then track the pass and fail rate of each test plan instance.
Generate Reports
- Testitool allows anyone to view a variety of different test plan reports including: a bug report, a progress report, and failure rate report, and more.
Import/Export Test Cases from Excel
- Do you prefer to use a program like Excel to write your test plans - Testitool allows users to easily import and export test plans and all of their test cases to and from CSV file formats.

newfile is a program for creating starter files, or trees of files, by processing templates with a C-preprocessor-like syntax.

newfile generates "starting-out" files using a full featured template preprocessor. It can also generate trees of files, for example, a FreeBSD port or a project using automake and autoconf.

A user can add their own template files and directories to those supplied with the package. It includes templates for making "empty" files for Ruby, make, shell, C, C++, C & C++ headers, and more.

Variables

Builtins

Some variables are built into the system, and should always be defined. Some will get default values if not defined.

TEMPLATE

The name of the template used to construct the current project or file(s).

NAME

The name of the input file, minus any directory prefix.

NAMEID

An identifier based on NAME.

PROJECT

If a project template is being expanded, this is the name of the template.

PROJECTID

An identifier based on PROJ.

LICENSE

Defined by the command line option -l/--license. Licenses are a special case of project templates, and their files are mixed in with a project templates file. In the case of a single file, the value of LICENSE determines which directory to search for a file called ``license that is included in the generated file.

AUTHOR

Defined by the command line option -a/--author. The name of the author of the code or document. If not given, taken from the users full name in the /etc/passwd file.

EMAIL

Defined by the command line option -e/--email. If not given, constructed from the users login name and the hostname.

ORGANIZATION

The organization to which the author belongs, in the context of the code or document being created. If not given, defaults to the value of AUTHOR.

OWNER

Defined by the command line option -o/--owner. The owner of the copyright. May be an arbitrary string, or one of the special strings ``org, ``organization, or ``author. If not given, defaults to ``author.

BODY

If defined, indicates to many templates to include extra boilerplate text to define a skeleton body for the file. See the individual templates for details. The shell and ruby templates are especially good examples, since these are the languages Ive been using most and these templates have received the most attention to detail.

ScramDisk for Linux (SD4L) is a suite of Linux tools and a graphical user interface (GUI) which allow the creation of, and access to ScramDisk encrypted container files. In particular, SD4L provides a Linux driver which enables mounting ScramDisk containers.
ScramDisk for Linux also encrypts partitions on a hard disk or storage media such as USB sticks or floppy disks entirely as devices. Version 1.0, moreover, supports TrueCrypt containers.
Enhancements:
- Fix for a bug in mounting ext3 file systems (Tracker 1746730). Check mounting ext3 before ext2 if mount option auto was chosen.
- Fix for a bug in case of file system mount failure (Tracker 1750002). Immediately unmount if mounting the file system failed.
- User access rights on block device containers are no longer checked before mounting because this commonly prevents normal users from mounting such containers (Tracker 1750005).