Free file systems compared software for linux

All System Info is a system info SuperKaramba theme. Simple english version...
It shows:
- System Info
- CPU usage
- Network Usage
- Memory Load
- HDD usage

File::DirCompare is a Perl module to compare two directories using callbacks.

SYNOPSIS

use File::DirCompare;

# Simple diff -r --brief replacement
use File::Basename;
File::DirCompare->compare($dir1, $dir2, sub {
my ($a, $b) = @_;
if (! $b) {
printf "Only in %s: %sn", dirname($a), basename($a);
} elsif (! $a) {
printf "Only in %s: %sn", dirname($b), basename($b);
} else {
print "Files $a and $b differn";
}
});

# Version-control like Deleted/Added/Modified listing
my (@listing, @modified); # use closure to collect results
File::DirCompare->compare(old_tree, new_tree), sub {
my ($a, $b) = @_;
if (! $b) {
push @listing, "D $a";
} elsif (! $a) {
push @listing, "A $b";
} else {
if (-f $a && -f $b) {
push @listing, "M $b";
push @modified, $b;
} else {
# One file, one directory - treat as delete + add
push @listing, "D $a";
push @listing, "A $b";
}
}
});

File::DirCompare is a perl module to compare two directories using a callback, invoked for all files that are different between the two directories, and for any files that exist only in one or other directory (unique files).
File::DirCompare has a single public compare() method, with the following signature:

File::DirCompare->compare($dir1, $dir2, $sub, $opts);

The first three arguments are required - $dir1 and $dir2 are paths to the two directories to be compared, and $sub is the subroutine reference called for all unique or different files. $opts is an optional hashref of options - see OPTIONS below.

The provided subroutine is called for all unique files, and for every pair of different files encountered, with the following signature:

$sub->($file1, $file2)

where $file1 and $file2 are the paths to the two files. For unique files i.e. where a file exists in only one directory, the subroutine is called with the other argument undef i.e. for:

$sub->($file1, undef)
$sub->(undef, $file2)

the first indicates $file1 exists only in the first directory given ($dir1), and the second indicates $file2 exists only in the second directory given ($dir2).

Yoxel Systems is a software product management and customer feedback management solution. Yoxel Systems is a connected system to track product requirements, manage product life cycles, provide online customer support, and accumulate support knowledge.

Yoxel Systems is more than yet another bug tracker, helpdesk or project organizer. It bridges request tracking and project management by providing a flow manager that walks your team from request prioritization and project planning through project implementation to project completion.

Unlike web based portals from SalesForce.Com or SugarCRM Yoxel Systems is tailored specifically for software development companies.

WHY YOXEL SW?

A role based, easy to use and very flexible request tracking system with customizable workflow, powerful filtering and advanced reporting capabilities.

Product management capabilities and agile methods of development on top of your existing Bugzilla/Mantis/GNATS/...

Automated process for product requirements management and product development planning/tracking.

Efficient collaboration between R&D, marketing and customer support teams to increase relevancy and value of your product releases.

Improved customer support that gives you fast and more accurate customer feedback on product requests and priorities.

WHY YOXEL IT?

The work of IT departments is not just about supporting users and resolving various network issues, it is also about implementing complex projects concerning. infrastructure and efficiency of your systems and business:

YOXEL IT is the solution for your IT department:

Ticket Tracking System is flexible and powerful, packed with features you expect from professional IT helpdesks.

Yoxel IT Project Management System extends TTS allowing your IT specialists to collaborate, plan and track complex IT projects.

Fast Secure File System exports existing directories securely over the network, letting users store and retrieve encrypted data in a scalable and transparent way. FSFS is written in C and works on GNU/Linux systems on x86 and PPC architectures, with help from FUSE and OpenSSL.
File systems are easily the most evident, from the point of view of users, component of an operating system. Through file systems it is possible to organize data in a wide variety of ways, and access resources through a common interface.
Users can nowadays not only store and retrieve documents, but also find information on running processes and system settings (through ProcFS), access and manipulate e-mail (for example with GmailFS), or perform several other operations.
In several circumstances and scenarios it is desirable to protect stored files and directories from manipulation by unknown or malicious users: financial or health-related data, confidential documents, or any kind of personal or sensitive data may need to be stored securely, in such a way that it can not be examined or modified freely by third parties.
Most file systems do not take action in this sense, and external cryptographic utilities are sometimes employed to secure data before storage. While this can be a perfectly secure solution, it is not transparent to users.
Distributed file systems propose efficient ways of accessing data remotely as if it resided on the local machine; when it comes to dealing with securely stored data as in the examples above, care must be taken to preserve confidentiality and integrity also during network transfer.
Not all distributed file systems accomplish this task, weakening the overall security of the system, or do so inefficiently, making it inconvenient for users.
FSFS is a secure, distributed file system in users space, written in C with much help from FUSE and OpenSSL. It lets users store and retrieve data securely and transparently, knowing that it is protected both on permanent storage devices and while in transit over the network.
It is also concerned with scalability, therefore separates data cryptography from the server, leaving it to the clients; this approach is similar to the one used in CFS, and opposite to those taken on by other secure file system solutions (like NFS on top of IPsec).
FSFS is written as a pair of user space daemons that act as client and server. Because of this, it needs no kernel support (unlike NFS over IPsec), save the FUSE loadable kernel module on clients, included in Linux since 2.6.14; servers dont use FUSE and depend only on user space OpenSSL libraries.
Servers export an existing file system (of virtually any kind) to clients over the network through two separate channels: a TLS connection set up with OpenSSL, and a clear channel. Requests from the clients to the servers are sent via the TLS socket, thus they are encrypted and authenticated, according to TLS v1 specifications, by the channel itself and decrypted on receipt, as they are usually very short and the relevant cryptography does not constitute a great overhead; simple server replies undergo the same process.
Cryptography in this case happens at both ends of the transmission.
In a distributed file system, large amounts of data may be transferred between clients and servers, thus encrypting and decrypting everything may become too cumbersome for both parties, and as more clients are added to the system the server may severely lose performance; moreover, file data should be stored encrypted anyway, so the cryptography could be moved to the clients, in such a way that each encrypts data before a write operation sends it over the network to the server, and decrypts it after a read retrieves it.
This way servers only deal with TLS details and can concentrate on serving client requests by doing the relevant I/O on the underlying, "physical" file system. As the data is already encrypted, it does not need to go through the TLS channel and the corresponding overhead, but can be sent via the clear channel, provided the messages are authenticated.
Enhancements:
- This release fixes two bugs. One bug related to socket creation and would cause problems on some systems (namely OpenSUSE 10.2). The other bug related to server configuration creation when using the Python configuration utilities. Users dont need to upgrade to this release if theyre not experiencing problems or are not using the Python configuration utilities.

Alphagate Systems Kernel Patchset provides new technologies and features, standard enhancements, as well as trivial-but-necessary fixes, that have not yet made it into the mainline (vanilla) Kernel.
So on one side, you get the next-gen code, while retaining stability is of concern. We choose SUSE Kernels because it is another stage of quality assurance that things do work reasonably.
2.6-AS22 is based on 2.6.15, which is quite a jump from 2.6.13. Certain things are missing because they are not available yet, such as TPROXY support. Because of this, AS21 and AS22 were released at the same time.
Components:
- Netfilter: IMQ, ROUTE, SYSRQ, TARPIT, XOR, connlimit, layer7, nth, random, u32, rICMP
- ttyrpld 2.10 rpldev
- CDFS 2.6.12
- BalaBit TPROXY 2.0.2 for 2.6.13
- SquashFS 2.2, +xmagic, +scan4it extensions
- UnionFS 20051130
- QuadDSP 1.2 - 4-channel audio output tools
- MultiAdmin 1.0.3
- THKD for Toshiba harddisks
- cdemu 0.7
- NDISwrapper 1.7
- RaLink RT2X00 drivers
- snd-pcsp audio driver and pcspkr emergency sound upon Oops, Panic or BUG
- Partition display upon rootfs mismount
- Boot time improvement by nosynchro RTC
- Visual plus: AS CKO, PureVGA, BSDUnderline, Con Loglevel, pipesize stat
- various /proc hardeners
- various small fixes (incl. UTF-8 console compose and userspace greediness fix)
- mouse button swap
- Staircase 13.2 provided (but not activated by default)
Enhancements:
- Unionfs, tproxy, sonypi, sony_acpi, the staircase scheduler, full preemption, and some other minor parts were updated.

Struct::Compare is a recursive diff for perl structures.

SYNOPSIS

use Struct::Compare;
my $is_different = compare($ref1, $ref2);

Compares two values of any type and structure and returns true if they are the same. It does a deep comparison of the structures, so a hash of a hash of a whatever will be compared correctly.

This is especially useful for writing unit tests for your modules!

PUBLIC FUNCTIONS

$bool = compare($var1, $var2)

Recursively compares $var1 to $var2, returning false if either structure is different than the other at any point. If both are undefined, it returns true as well, because that is considered equal.

LMS (LAN Management System) is the integrated system of networks management designed for various size internet providers (ISP).

That software writed in PHP, Perl and C, works with variuos database systems.