Free officer ricky software for linux

FIRST LIVE primarily it is to assist law enforcement agencies and its officer to combat cyber terrorism and other malicious activities. FIRST LIVECD usage and application can be also extended to private organizations and individuals who are need alternative in securing their network and computer system. FIRST LIVECD objectives are to capture and to provide an immediate environment (workspace) to perform live:

1. Computer Forensics Analysis
2. Incident Response
3. Data Acquisition And Recovery
4. Virus Scanning And Detection
5. Vulnerability Assessment
6. Runs On Any x86 Computer Without Any Installation
7. One Stop Solutions For Fast Deployment And Low Cost Security Product.
8. User Friendly

UFFS is an ultra low cost flash file system for embedded system.
UFFS is a NAND flash file system designed for embedded system, it performs some unique and advanced features:
Low cost:
For NAND flash with 512 page size:
NAND flash | Total Blocks | Buffers/Caches | Total RAM cost
128M | 8192 | 40/30 | 164K
32M | 2048 | 40/30 | 68K
16M | 1024 | 10/10 | 26K
Tree Nodes: 16 * toatl_blocks
Page Buffers: page_size(512) * buffers (10 ~ pages_per_block)
Block info caches: (14 * pages_per_block) * block_info_caches ( 5 ~ 20)
Total Memory usage = Tree Nodes + Page Buffers + Block info caches + Others(1~2K)
For NAND flash with 2K page size:
NAND flash | Total Blocks | Buffers/Caches | Total RAM cost
512M | 8192 | 40/30 | 180K
128M | 512 | 40/30 | 70K
Tree Nodes: 16 * toatl_blocks
Page Buffers: page_size(2048) * buffers (10 ~ pages_per_block)
Block info caches: (14 * pages_per_block) * block_info_caches ( 5 ~ 20)
Total Memory usage = Tree Nodes + Page Buffers + Block info caches + Others(1~2K)
Fast booting
UFFS read only one spare area for each NAND flash block to build up the in-memory nodes tree. Typically, UFFS needs less then 1 second to mount a full loaded 128 Mbytes NAND flash.
Superb Reliability
Guaranteed integrity across unexpected power losses.
Bad-block tolerant, ECC enable and ware-leveling
Nothing new for flash file system, but UFFS implements these in a simple yet effective way.
No garbage collection needed for UFFS
UFFS collect the dirty blocks on the fly, no garbage collection needed.
Support direct flash interface, no operating system needed
UFFS can be build on top of direct flash interface,easy to port to any embedded system.
Fully tested
UFFS is fully tested on PC (via UFFS PC emulator). Moreover, UFFS is not just proof-of-concept but has been successfully used in real world product for tens of thousands of copies.
What UFFS "IS", "IS NOT" ?
UFFS is not a Linux kernel module.
UFFS is not running in a separated thread rather than application.
UFFS is a library to be linked with your embedded application.
UFFS should be used when JFFS/YAFFS cant be used (because of the insufficient of memory)
UFFS is not the substitute of JFFS or YAFFS.
Why UFFS ?
- Hardware resource is limited (typically 64~512K RAM), but need a reliable flash file system
- JFFS/JFFS2 sucks (useless without Linux/MTD, also memory monster)
- YAFFS/YAFFS2 is excellent, but still consumes too much memory
- Others ? ... not available... (open source of course)
Enhancements:
- Support large page size, e.g. 1K, 2K, support all Samsung NAND flash.

Open Admin for Schools is a School Administration Program. It is a freely available, open source software package and is licensed under the GNU General Public License.
Open Administration for Schools project is entirely web based and can run from a centrally located division wide server or a single computer in a school. It is designed to support an entire division on one or more central computers but can also work just fine for a single school.
Currently several school divisions use this approach and have 15+ schools on a single central server. This is because it is designed to be lightweight both in server resource requirements and in communication bandwidth.
It is secure. Each school has two or more virtual websites and each is protected with password(s). One site, the admin site, is used by the school office and another, the teacher site, is used by teachers in the classroom.
The teacher site also has password access for entering attendance by teachers and also uses cookies that expire in a short period, further limiting access. Another site, a parent/student site, is controlled by parent/student userids and passwords. A fourth virtual site may be used by school liason officers from outside agencies to give them a slightly different access to school information. (Community Schools)
Main features:
- Demographics - It stores student and family information that can be viewed and printed in a variety of ways.
- Attendance - Attendance can be entered either by secretaries in the school office or by teachers in the classroom. It features the ability to do different numbers of periods per day for elementary grades vs high school and middle years. This will allow elementary classes to have 2 classes per day (AM/PM) with a homeroom teacher while higher grades can have attendance done on a per subject period basis (and be subject based). Attendance reports are integrated with report cards/progress reports. A variety of attendance reports are available. A variety of attendance entry methods are available for use by teachers and/or secretaries to allow it to integrate with normal school practice.
- Discipline - A simple discipline module to track student discipline events and track outcomes, etc. Behaviours may be categorized and statistical reports may be printed. Enrollment changes are also posted into this system.
- Report Card System - a flexible reporting system with per subject objectives (up to 20), integrated attendance reporting, etc. All report cards are printed as PDF reports and may include a school logo. All subjects may have unlimited length text comments, and can have any desired ordering. Attendance reporting will now do days open, days enrolled, days absent, and times late as standard.
- IEP (Special Needs) Site that is integrated at the division level that allows special needs teachers to tailor individual student programs that can be viewed from each schools teacher site. This includes the ability to add student medical history, testing done, student teams (and responsibilities), and objectives chosen from lists of thousands, categorized in a variety of ways. There can be up to 32 objectives per subject and each subject is specific to that particular child. His/her program would consist of a variety of subjects in areas such as fine motor control, etc.
- This system can generate progress reports (for use with the report card system) as well as a comprehensive IEP report containing the yearly plan for the child. This IEP can also viewed from the teacher site, to ensure compliance throughout the year.
- Export/Import Modules - to allow students to easily transfer schools within divisions without re-entry of demographic information. Export of data to other programs. Export of data to Provincial authorities via an automated XML based transfer mechanism.
- Saskatchewan SDS support for direct XML transfers of student demographic, subject and enrollment marks to provincial authorities.
- Online Gradebook to allow teachers to enter marks and assessments onine from school or home. It can group and weight assessment items and post directly into the report card system.
- Parent Viewing scripts to allow parents to view attendance, gradebook(where allowed), and report card marks. This is easily integrated into existing school sites.
- Upcoming: Family functions, Parent-Teacher Interview Scheduling, Wherever schools want to go...
- Further out... Multi-language support (demand for a Spanish version exists currently), Student timetabling.
Enhancements:
- A new Fees System to allow fee charging (predefined or new, with various groups), invoice printing, payments and receipts, and the ability to export summary journal transactions to an external accounting program.
- A new teacher logout to remove session data has been added.
- There is a new 70 page User Documentation PDF and a 40 page Administration Documentation PDF (also available in HTML versions).

Test::STDmaker is a Perl module to generate test scripts, demo scripts from a test description short hand.

SYNOPSIS

#######
# Procedural (subroutine) interface
#
use Test::STDmake qw(find_t_roots get_data perl_command);

@t_path = find_t_paths()
$date = get_date();
$myperl = perl_command();

#####
# Class interface
#
use Test::STDmaker

$std = new Test::STDmaker( @options ); # From File::Maker

$success = $std->check_db($std_pm);
@t_path = $std->find_t_paths()
$date = $std->get_date();
$myperl = $std->perl_command();

$std->tmake( @targets, %options );
$std->tmake( @targets );
$std->tmake( %options );

######
# Internal (Private) Methods
#
$success = $std->build($std_driver_class);
$success = $std->generate();
$success = $std->print($file_out);

The Test::STDmaker program module provides the following capabilities:
Automate Perl related programming needed to create a test script resulting in reduction of time and cost.

Translate a short hand Software Test Description (STD) file into a Perl test script that eventually makes use of the Test module.

Translate the sort hand STD data file into a Perl demo script that demonstrates the features of the the module under test.

Provide in the POD of a STD file information required by a Military/Federal Government Software Test Description (STD) document that may easily be index and accessed by automated Test software. ISO, British Military require most of the same information, US agencies such as the FAA. The difference is that ISO, British Military do not dictate detail format. US agencies such as FAA will generally tailor down the DOD required formats.

Thus, there is an extremely wide variation in the format of the same information among ISO certified comericial activities and militaries other than US. Once the information is in a POD, different translators may format nearly exactly as dictated by the end user, whether it is the US DOD, ISO certified commericial activity, British Military or whoever. By being able to provide the most demanding, which is usually US DOD, the capabilities are there for all the others.

The Test::STDmaker package relieves the designer and developer from the burden of filling out word processor boiler plate templates (whether run-off, Word, or vi), counting oks, providing documentation examples, tracing tests to test requirments, making sure it is in the proper corporate, ISO or military format, and other such extremely time consuming, boring, development support tasks. Instead the designers and developers need only to fill in a form using a test description short hand. The Test::STDmaker will take it from there and automatically and quickly generate the desired test scripts, demo scripts, and test description documents.

Look at the economics. It does not make economically sense to have expensive talent do this work. In does not even make economically sense to take a bright 16 year, at mimimum wage and have him manually count oks. Perl can count those oks much much cheaper and it is so easily to automated with Perl. And something like this were you are doing it year in and year out, the saving are enormous. To a program manager or contract officer, this is what programming and computers are all about, saving money and increasing productivity, not object oriented oriented programing, gotos or other such things.

The Test::STDmaker class package automates the generation of Software Test Descriptions (STD) Plain Old Documentation (POD), test scripts, demonstrations scripts and the execution of the generated test scripts and demonstration scripts. It will automatically insert the output from the demonstration script into the POD -headx Demonstration section of the file being tested.

exmats goal is to provide an easy to use, yet very efficient matrix library. Overloaded operators allow to write algebraic expressions like v=A*u +u in C++, instead of bunch of boring functions.
This syntactic sugar comes with runtime cost, one way to eliminate the overhead is to use Expression Templates (ET).
Using ET, we can further boost up the efficient by analyzing the expression at compile time and generate the most efficient code for that expression.
This library is still under early development.
Main features:
Generic:
- The element type of the matrix is generic, it can be any type of the C++ build-in type like int, float, double.
- Other types like complex or arbitrary precision type can also be used as the element type.
- Matrix expression can be make up of any element type, that is, an integer matrix can be added to a float matrix and then assign to a double matrix.
Easy to use:
- You can write matrix expression using +, -, *, / operators as usual mathematic notation.
Safe:
- There are 3 levels of error checking policy you can apply on each class of matrix.
Efficient:
- Specialized, hand made comparable optimized code can be generated for different expressions.
- SIMD code can be used on small size matrix.
- Provide a interface to use BLAS as the math kernel, which is highly optimized for out of cache operations.
Enhancements:
- Cross product bug fixed
- Added determinant, minor view, cofactor view and adjoint view for matrix
- Added support for column major memory layout
- Helper macro for deriving ET enabled sub-class from exmat::Mat easily
- Array version for approximated math