Free flat file software for linux

Flat File Extractor can be used for reading different flat file structures and printing them in different formats. ffe is a command line tool developed in GNU/Linux environment and it is distributed under GNU General Public License 2 or later.
Main areas of use are:
- Extracting particular fields or records from a flat file
- Converting data from one format to an other, e.g. from CSV to fixed length
- Verifying a flat file structure
- Testing tool for flat file development
- Displaying flat file content in human readable form
Main features:
- Command-line tool
- Reads standard input and writes to standard output as default
- One input file can contain several types of records (lines)
- Fields in a flat file can be fixed length or separated
- Input file structure and output definitions are independent, meaning one output format can be used with several input files
- Input file structure and output format are freely configurable, they are not predefined
- Output can be formatted e.g. as: fixed length, separated, tokenized, XML, SQL,...
- ffe tries to guess the input format, user needs not to give it as a parameter
Enhancements:
- Configuration keyword const has been added

Flatworm project is a Java library intended to allow a developer to describe the format of a flat file using an XML definition file, and then to be able to automatically read lines from that file, and have one or more beans be instantiated for each logical record.

There are a few powerful features in Flatworm worth mentioning. For one thing, a record may consist of one or more physical lines in the file. A record may contain more than one bean once decoded. A flat file may contain more than one type of record, and Flatworm can use line length and substring matching to determine which type of record a line begins.

Besides fielded buffer flat files, Flatworm also supports text files where the different fields are separated by a separator character, e.g. CSV (comma separated values) files.

Last but not least, Flatworm is able to produce flat files from beans and the same definition file.

The flat assembler is a fast and efficient self-assembling 80x86 assembler for DOS, Windows, and Linux operating systems. Currently, it supports all 8086-80486/Pentium instructions with MMX, SSE, SSE2, SSE3, and 3DNow! extensions.
It can produce output in binary, MZ, PE, COFF, or ELF format. Flat Assembler includes the powerful but easy-to-use macroinstruction support, and does multiple passes to optimize the instruction codes for size. The flat assembler is entirely written in assembly language.
Enhancements:
- 32-bit relocations are now allowed in PE64 output format.
- EIP-relative addressing was added.
- The PLT operator was added for the ELF output format.
- SSSE3 (Supplemental SSE3) instructions were added.
- Some Win64 headers and examples were provided in the Windows package.
- The SYSRETQ mnemonic was added, and RDMSRQ/WRMSRQ/SYSEXITQ mnemonics were added for the 64-bit variants of respective instructions.
- R8L-R15L (Intel-style) aliases were added for R8B-R15B registers. Support for the AMD SVM technology instructions was added. Numerous bugs were fixed.

FLAT::Legacy::FA::RE is a regular expression base class.

SYNOPSIS

use FLAT::Legacy::FA::RE;
use FLAT::Legacy::FA::NFA;
my $re = RE->new();
$re->set_re(a|b|(hi)*);
my $nfa = $re->to_nfa();
print $nfa->info(); # see stuff on NFA
my $dfa = $nfa->to_dfa();
print $dfa->info(); # see stuff on DFA
my @removed = $dfa->minimize();
print $dfa->info(); # see stuff on minimized DFA
print "Removed ".($#removed+1)." statesn";

This module implements a regular expression parser, and supports the conversion of a RE to a deterministic finite automata. A homegrown recursive descent parser is used to build the parse tree, and the method used to conver the regular expression to a DFA uses no intermediate NFA.
Recursive Descent-safe Regex Grammar:

R -> O

O -> CO

O -> | CO | epsilon

C -> SC

C -> .SC | epsilon

S -> LS

S -> *S | epsilon

L -> a | b | c |..| 0 | 1 | 2 |..| (R) | epsilon

Terminal symbols: a,b,c,..,z,0,1,2,..,9,|,*,(,)

NOTE: Concatenation operator, ., is not a terminal symbol and should not be included in the regex

FAQ: Q: Does this support Perl regular expressions?
A: No, just the regular expression using the terminal symbols listed above.

Intelligent Wardialer is a "war dialer" used for auditing your PSTN (phone) network. Its features include random/sequential dialing, Voice over IP using the IAX2 (Intra-Asterisk eXchange) protocol, ASCII flat file and MySQL logging, a curses-based front end, key stroke marking, multiple modem support, several methods of "tone detection", save/load state, banner detections (to determine remote system types) and blacklist support.
Main features:
- Full and Normal logging: Full logging records all possible events during dialing (busy signals, no answers, carriers, etc). By default it only records things that we might find interesting (carriers, possible telco equipment).
- ASCII flat file and MySQL logging: You can log to a traditional ASCII flat file, and record information into a MySQL database.
- Dials randomly or sequentially.
- Remote system identification: When finding a remote modem and connecting, iWar will remain connected and attempt to identify the remote system type.
- Key stroke marking: When actively "listening" to iWar work, if you hear something interesting, you can manually "mark" it by hitting a key. You can also enter a "note" about something you find interesting.
- Multiple modem support, because... well, hey - this is "Unix". iWar will support as many modems you can hook up
- Nice "curses" based display. This means that if youre using iWar from a Linux console or a VT100 based terminal, it should work fine. Its not a escape sequence kludge, but true "curses".
- Full control over the modem: Unlike other kludges, iWar doesnt just open the modem as a typical "file". It controls the baud rate, parity, and CTS/RTS (Hardware flow control) DTR (Data terminal ready). This is important for controlling the modem and making it preform the way you want it to during scanning. For example, DTR hang ups.
- Blacklisted phone number support: For numbers the system should never dial.
- Save state: If within the middle of a "wardialing" session you want to quit, you can save the current state to a file. This allows you to come back later and restart iWar where you left off. (via the -l option)
- Load pre-generated numbers: You can load a file (via the -L option) of numbers that you want to dial. This is useful if you want to load numbers generated by another routine (perl/shell script/etc).
- Tone location, if your modem supports it. iWar uses two different methods. The traditional "ATDT5551212w;" (Toneloc) and "silence" detection.
- Records remote system banners on connection for later review
- iWar can be used to attack PBXs and Voice mail systems
- Terminal window so you can watch modem interactions and carrier results in real time
- Support the IAX2 (Intra-Asterisk eXchange) "Voice over IP" (VoIP) protocol. This allows you to scan without the need of additional hardware! To my knowledge, iWar is the first war dialer with VoIP functionality
- In IAX2 mode, iWar acts as a "full blown" VoIP client. In this mode, key 0-9, * and # play there DTMF equivalents. In this mode, you can also directly "talk" (using a microphone) with the remote target if so desired.
- In IAX2 mode, if your VoIP provider supports it, you can "set" your caller ID number (caller ID spoofing).
- Comes with complete source code and is released under the GNU General Public License.
Enhancements:
- Major bugfixes were made for BSD type systems.
- Some other minor bugs were also fixed. VoIP IAX2 (Intra-Asterisk eXchange) support was added.
- With this, you can scan with no additional hardware (such as an analog modem).
- Instead, calls are placed over the Internet.
- DTMF support for when under IAX2 mode was added.

file*HANDLER project is primarily a Perl script which coordinates some free media conversion packages (cited later) with a PostgreSQL back end accessing server to index and serve binary and text files direct from the database. A simple CGI file with embedded AJAX makes calls to this server which is also constantly looking for other alive f*H servers on the Internet.
Since the server caches media into the SQL database on demand, as the network grows, the network improves.
Its gridded directory sharing/browsing/searching with streaming audio/video as well as flat text/doc/pdf/image display for everyone. Its written with a few hooks for tags that would be included in your actual front page so that the UI is discard-able -- anyone can quickly rewrite a whole new [GT]UI without having to worry about the syntax of the newest version of dojo.licio.r or whatever.
If you wanted to ignore the JS/HTML/CSS hooks then you can easily use the system to make direct requests that just return lists formatted as HTML table-bodies. In other words, the markup IS the markup.
As such, Ive whipped up a Dojo 0.2 Widget that coordinates the serving backend with a UI so anyone can embed f*H functionality anywhere, or easily customize a provided default page.
A file*HANDLER server is really a few constituent parts Ive tied up for you (top down):
- A local web page providing the UI(served by an HTTP server of your choice) that is generated by a cgi script with embedded AJAX.
- A secondary portion of the same CGI script, acting as middle-ware, which communicates, via AJAX, with the local front page to reconcile asynchronous JavaScript requests with the file*HANDLER sub-network back-end.
- An always-on network server written in PERL that serves to the front and end communicates laterally with everyone elses file*HANDLER back-end PERL server additionally, it manages indexing of content directories you choose to serve.
- A PostgreSQL database that is accessed only via internal PERL routines called from your front page.
So for example, a remote user comes to your site. First, not only can they browse and search your files, but they can also browse and search the files of anyone else hosting a file*HANDLER server that your local server knows about. (file*HANDLER identifies other servers on the network automatically). The user can now read/view/listen/watch by stream any content they find from whomevers server. Theres no download, so theres so actual sharing, just direct streaming to the users browser.

Plans is a powerful and flexible Web calendar. Plans has features like recurring events, merged calendars, event icons, custom themes and templates, MS Outlook export, SQL or flat-file data storage, and browser-based management.
Main features:
Multiple Calendars
- One installation of plans can support many calendars.
- Calendars can share information with each other.
- Each calendar is managed independently (unique password, custom options, custom look & feel).
- Multiple calendars running on the same installation of plans can be "embedded" in completely different websites.
Recurring Events
- Plans uses a powerful and flexible recurring event model.
International Support
- Plans supports multiple languages.
- Weeks can start on days other than Sunday.
- Plans supports arbitrary date formats (mm/dd/yy, dd/mm/yy, etc.)
Database Support
- Plans can store data in flat files or an SQL database.
Sharp-looking
- Plans is the nicest-looking web calendar.
- Plans has several downloadable themes available.
- CSS-based layout makes it easy to match the colors & fonts with your website.
Open Source
- Plans is licensed under the GPL. You can freely modify the code for your needs. Many organizations have done so.
Extendable
- Plans architecture allows add-ons and standalone programs to re-use its framework.
- Plans can export events to other platforms, including MS Outlook and Palm.
Template-based design
- Plans uses HTML templates to allow easy customization of the look & feel.
- Each calendar can have its own custom template, even located on a different server.