Free flat files software for linux

Fastilo project is a freeware shopping cart script based on PHP and Flat Files. Extremely easy to run and use. Our product work on Quick.Cart engine with some modifications.
Main features:
- full administration of the products, categories and delivery companies (delivery cost)
- full administration of the orders
- system for managing the content of additional pages and (subpages) in the web shop, as the company information, regulations etc.
- printing products and order cards
- system of additions, which helps to make your web shop even more functional
- inventory stock control
- WYSIWYG editor
- bestsellers panel
- email customer with his order
- friendly links

Tie::FlatFile::Array is a Perl extension which treats a flatfile database as an array of arrays.

This module allows the programmer to treat a flatfile database as as array of arrays. For example, lets say you have a datafile that has fixed-length records like so:

Field-name Type
URL ASCII characters, length 30
Referals Integer, 4 bytes, binary in network order

If you were going to use pack to create a record like this, youd use a format string of A30N. Since Tie::FlatFile::Array does the packing and unpacking behind the scenes, you would use that pack format string in the call to tie:

tie @flat, Tie::FlatFile::Array, data.file,
O_RDWR | O_CREAT, 0644, { packformat => A30N }
or die("Tie failure: $!");

To insert an item into the data file, you would assign an array reference to one of the arrays elements like so:

$flat[0] = [ www.yahoo.com, 3601 ];

A Simple TimeSheet (ASTS) allows a group of people to record the hours spent working on a variety of projects. For each project, the hours can be divided into a number of different tasks. There are global projects and tasks but also personal projects and tasks for each user.
The main aim is to provide tools which are easy for the user to install and manage.
The tools will be implemented with as few external dependencies as possible. They will not, for example, depend on a database for storage but use flat files (maybe XML format) instead. ASTS, for example, requires just perl and the CGI and Date::Calc perl modules.
More sophisticated versions of the tools may be added in the future.
Enhancements:
- Custom data fields can be defined.
- Project and task lists can now include separators.
- Bugs were fixed.
- The documentation was updated.

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.

Autofs NG is a Linux automounter that is intended to be completely interoperable with autofs implementations on other Unix platforms. As such, it supports some features that the current Linux automounters do not.
This includes direct mounts, /net (--hosts access), lazy mounting and unmounting of hierarchical multimounts, and browsing. Autofsng also supports the usual indirect map support available elsewhere.
Maps are supported from flat files, executable maps, NIS maps, NIS+ maps, LDAP maps, and hesiod (DNS) filsys namespace.
AutofsNG was originally developed at Sun Microsystems, but has been cancelled as a project. Fortunately, it has been released as GPL, so I am continuing its development in my spare time.
Enhancements:
- Initscript fixup for path to /proc/mounts
- We no longer update /etc/mtab because the kernel does all unmounting. Current recommendation is to symlink /proc/mounts to /etc/mtab if you want to see the what is actually mounted with calling mount
- Fixed SuSE/LSB initscript issue where ypbind wasnt neccesarily started before autofsng.
- Added an RPM .spec file to the tree.
- Fixed initscript install
- Fixed possible crash when using the -hosts map.
- Redimentary mount option translation. Currently translates the common Solaris NFS mount options to Linux specific ones. Hard-coded.
- Initscript fixups for unknown systems (Debian in particular)
- Fixed a bug where the -hosts map would return duplicate map offsets, which is a semantic error for usual entries.

File::Tabular can search and edit flat tabular files.

SYNOPSIS

use File::Tabular;
my $f = new File::Tabular($filename);

my $row = $f->fetchrow;
print $row->{field1}, $row->{field2};

$row = $f->fetchrow(where => someWord);
$row = $f->fetchrow(where => field1 > 4 AND field2 >= "01.01.2001");
$row = $f->fetchrow(where => qr/somes+(complexs*)?(regex|regular expression)/i);

$f->rewind;
my $rows = $f->fetchall(where => someField =~ ^[abc]+);
print $_->{someField} foreach @$rows;

$f->rewind;
$rows = $f->fetchall(where => +field1:someWord -field2:otherWord,
orderBy => field3, field6:num, field5:-alpha);

$f->rewind;
my $hashRows = $f->fetchall(where => foo AND NOT bar,
key => someField);
print $hashRows->{someKey}{someOtherField};

# open for updates, and remember the updates in a journal file
$f = new File::Tabular("+>$journalFile"});

# updates at specific positions (line numbers)
$f->splices(4 => 2, undef, # delete 2 lines from position 4
7 => 1, {f1 => $v1, f2 => $v2, ...}, # replace line 7
9 => 0, { ...}, # insert 1 new line at position 9
22 => 0, [{...}, {...}, ...] # insert several lines at pos. 22
...
-1 => 0, [{...}, {...}, ...] # append at the end
);

# shorthand to add new data at the end
$f->append({f1 => $v1, f2 => $v2, ...});
# same thing, but use the "Hash::Type" associated to the file
$f->append($f->ht->new($v1, $v2, ...));


$f->clear; # removes all data (but keeps the header line)

# updates at specific keys, corresponding to @keyFields
$f->writeKeys({key1 => {f1 => $v1, f2 => $v2, ...}, # add or update
key2 => undef, # remove
...
}, @keyFields);


# replay the updates on a backup file
my $bck = new File::Tabular("+<<less