Free safety software for linux

SQLAlchemy is a SQL toolkit and object relational mapper for Python.
The Python SQL toolkit and Object Relational Mapper that gives application developers the full power and flexibility of SQL. SQLAlchemy provides a full suite of well known enterprise-level persistence patterns, designed for efficient and high-performing database access, adapted into a simple and Pythonic domain language.
- extremely easy to use for all the basic tasks, such as: accessing thread-safe and pooled connections, constructing SQL from Python expressions, finding object instances, and commiting object modifications back to the database.
- powerful enough for complicated tasks, such as: eager load a graph of objects and their dependencies via joins; map recursive adjacency structures automatically; map objects to not just tables but to any arbitrary join or select statement; combine multiple tables together to load whole sets of otherwise unrelated objects from a single result set; commit entire graphs of object changes in one step.
- built to conform to what DBAs demand, including the ability to swap out generated SQL with hand-optimized statements, full usage of bind parameters for all literal values, fully transactionalized and consistent updates using Unit of Work.
- modular. Different parts of SQLAlchemy can be used independently of the rest, including the connection pool, SQL construction, and ORM. SQLAlchemy is constructed in an open style that allows plenty of customization, with an architecture that supports custom datatypes, custom SQL extensions, and ORM plugins which can augment or extend mapping functionality.
SQLAlchemys Philosophy:
- SQL databases behave less and less like object collections the more size and performance start to matter; object collections behave less and less like tables and rows the more abstraction starts to matter. SQLAlchemy aims to accomodate both of these principles.
- Your classes arent tables, and your objects arent rows. Databases arent just collections of tables; theyre relational algebra engines. You dont have to select from just tables, you can select from joins, subqueries, and unions. Database and domain concepts should be visibly decoupled from the beginning, allowing both sides to develop to their full potential.
- For example, table metadata (objects that describe tables) are declared distinctly from the classes theyre designed to store. That way database relationship concepts dont interfere with your object design concepts, and vice-versa; the transition from table-mapping to selectable-mapping is seamless; a class can be mapped against the database in more than one way. SQLAlchemy provides a powerful mapping layer that can work as automatically or as manually as you choose, determining relationships based on foreign keys or letting you define the join conditions explicitly, to bridge the gap between database and domain.
SQLAlchemys Advantages:
- The Unit Of Work system organizes pending CRUD operations into queues and commits them all in one batch. It then performs a topological "dependency sort" of all items to be committed and deleted and groups redundant statements together. This produces the maxiumum efficiency and transaction safety, and minimizes chances of deadlocks. Modeled after Fowlers "Unit of Work" pattern as well as Java Hibernate.
- Function-based query construction allows boolean expressions, operators, functions, table aliases, selectable subqueries, create/update/insert/delete queries, correlated updates, correlated EXISTS clauses, UNION clauses, inner and outer joins, bind parameters, free mixing of literal text within expressions, as little or as much as desired. Query-compilation is vendor-specific; the same query object can be compiled into any number of resulting SQL strings depending on its compilation algorithm.
- Database mapping and class design are totally separate. Persisted objects have no subclassing requirement (other than object) and are POPOs : plain old Python objects. They retain serializability (pickling) for usage in various caching systems and session objects. SQLAlchemy "decorates" classes with non-intrusive property accessors to automatically log object creates and modifications with the UnitOfWork engine, to lazyload related data, as well as to track attribute change histories.
- Custom list classes can be used with eagerly or lazily loaded child object lists, allowing rich relationships to be created on the fly as SQLAlchemy appends child objects to an object attribute.
- Composite (multiple-column) primary keys are supported, as are "association" objects that represent the middle of a "many-to-many" relationship.
- Self-referential tables and mappers are supported. Adjacency list structures can be created, saved, and deleted with proper cascading, with no extra programming.
- Data mapping can be used in a row-based manner. Any bizarre hyper-optimized query that you or your DBA can cook up, you can run in SQLAlchemy, and as long as it returns the expected columns within a rowset, you can get your objects from it. For a rowset that contains more than one kind of object per row, multiple mappers can be chained together to return multiple object instance lists from a single database round trip.
- The type system allows pre- and post- processing of data, both at the bind parameter and the result set level. User-defined types can be freely mixed with built-in types. Generic types as well as SQL-specific types are available.

jsfirewall increases the safety for the desktop PC with one network card.
The program is quickly administrated and it is easy to generate an iptables based firewall script.
It has no ROUTER function, but is a personal firewall and it is developed for use behind a router or for direct connections like ppp over ethernet.
jsfirewall uses the program "dialog", you can use it either on the X server or on the console.
Advanced features are built in and you can save or view logging files, tuning the logging and the kernel parameters, save and load, or delete, generated firewall templates.
There is optional support for an additional portrange as the default and you can give one command owner for every chosen port.
Installation:
Unpack the tar ball: tar xzf jsfirewall-0.7.1.tar.gz
cd jsfirewall-0.7.1
Open the file jsfirewall.conf and change the settings if you want (e.g. with vi).
Run ./install.sh in the console.
OPTIONS: install, update, cancel
Enhancements:
- A completly new config section was written.
- You can now edit in the "config" menu directly like in the "global" menu. jsfirewall now supports OpenVPN and can generate an OpenVPN styled firewall script.
- Help can now support all languages.
- All sections of the code were split into scripts.
- The program is now faster and open for other GUI languages and iptables based generator scripts.
- I The LANG variable in 0.7.1 was renamed to LANGU.

X2J is an XML binding framework which performs validation, serialization, and deserialization without the use of XSDs.

Instead, X2J project incorporates the strength of Annotations.


Unit testing is cruicial. If there is Anything you can say about the tools you need in order to create a framework, is that creating unit tests is your safety net when you decide to refactor it completely (and any framework, at its first steps, might go through such a thing - Nothing is ever fully designed for a future feature, not even a complete product.)

A few weeks ago I decided to have a major change to the way X2J analysation works, and use moulds and visitors instead of the previous, "everything-in-one-method" way. This change has worked great for me, but it was scary: What if X2J stopped working?

Sure, I could rollback the code - But that would serve to no good as I still needed this type of change. So I started writing tests. They werent JUnit tests, but just regular applications running X2J for me to manually check the results with. It worked, as amateur as it was, and I made the switch.

However, today I face another refactoring of code and I know I cant do the same thing over again. I need some stability to my code. Some red lights to appear when I do something that risked a totally different part of my application. Something that will tell me almost precisely where I broke the code.

This is where JUnits come in, and if you havent been using them, you should do so now. Im going to start creating them, starting this week. Only then will I tend to my refactoring tasks.

Instant is a Python module that allows for instant inlining of C and C++ code in Python. Instant is a small Python module built on top of SWIG.

Example of use:

>>> c_code = """
double sum(double a, double b){
return a+b;
}
"""
>>> import Instant
>>> ext = Instant.Instant()
>>>
>>> # create the wrapper code, compile and link it to a shared library
>>> ext.create_extension(code=c_code, module=test1_ext)
>>>
>>> # use the C code
>>> from test1_ext import sum
>>> print sum(3.7, 4.8)
8.5

Example with NumPy arrays converted to C double arrays:

>>> import Instant
>>> import Numeric
>>> import sys
>>> import time
>>>
>>> ext = Instant.Instant()
>>>
>>> c_code = """
/* add function for vectors with all safety checks removed ..*/
void add(int n1, double* array1, int n2, double* array2, int n3, double* array3){
for (int i=0; i >>"""
>>>
>>> ext.create_extension(code=c_code, headers=["arrayobject.h"],
>>> include_dirs=[sys.prefix + "/include/python" + sys.version[:3] + "/Numeric"],
>>> init_code=import_array();, module=test3_ext,
>>> arrays = [[n1, array1],[n2, array2],[n3, array3]])
>>>
>>> from test3_ext import add
>>> a = Numeric.arange(10000); a = Numeric.sin(a)
>>> b = Numeric.arange(10000); b = Numeric.cos(b)
>>> c = Numeric.arange(10000); c = Numeric.cos(c)
>>>
>>>add(a,b,c)

SimCList project is a high quality C library for handling lists.
SimCList is available for free, under restrictions imposed by the BSD license.
SimCList API is good because:
- it is simple, yet powerful
- it makes elegant and consistent use of information hiding
- it abstracts the actual data type to store
- it is fairly total
The library itself is very performant and makes a good compromise between performance in terms of time and space:
- insertion is O(n) [typically n/8]
- extraction and deletion are O(n) [typically n/8]
- iteration is O(1)
- sorting is always O(n logn), without worst case
Thread safety
The SimCList library is thread safe, meaning that many threads can run SimCList operators on different lists concurrently without hurt, or also read operations on the same list.
However, of course, no safety guarantee is made for performing concurrently write+write or read+write operations on the same list (eg: insertion, deletion, sorting, ...). For performance and portability reasons, protecting such operations from concurrency is left to the library adopter.
Performance
SimCList has been designed with ease to use and performance in mind. There is some example factors that have been taken into account, and against which the code has been optimized when implementing SimCList:
- overhead of function calls
- cache locality
- number of branches, possible CPU stalls or pipeline flushes
- dynamic memory allocation weight on the OS
- other mathematic/probabilistic optimizations for avoiding worst-case or improving average case behaviours in algorithms
Many parts of SimCLists code have been deeply improved with profiling analysis.
Enhancements:
- Transparent inclusion in C++ applications is natively supported.
- Sentinels are used to improve performance on list traversals.
- A problem was fixed with list_insert_at, which could output inconsistent lists when inserting into even-sized lists in position 0.

STLport is a multiplatform C++ Standard Library (STL implementation). Many compilers and operational environments supported. Standard (ISO/IEC 14882) compliance. Maximum efficiency. Exception and thread safety. Debug mode.
The company was started back in 1997 by a small group of developers gathered around STLport Standard Library Project. Since then STLport has been accepted by the technical community as industry standard for multiplatform development.
Over the years, we have been able to attract top-notch professionals, who currently provide on- and off-site consulting services to hi-tech businesses in Silicon Valley and nationwide. The reputation of STLport main product and variety of skills of the STLport has allowed us to win several substantial custom software development contracts.
Enhancements:
- Add support for EVC 2005 thanks Ulrich Echkardt.
- Modification of the code use to detect stateless classes to avoid a Visual Studio 2005 warning.
- Change configuration for Visual Studio 98, do not support explicit instanciation of class template method like locale::combine or bitset::to_string.
- Fix definition of the internal _STLP_WIN32_VERSION macro giving targeted platform version, based on WINVER or _WIN32_VERSION in this order.
- Fix a use of strncpy_s that was potentially leading to a crash.

Locale::TextDomain is a Perl Interface to Uniforum Message Translation.

SYNOPSIS

use Locale::TextDomain (my-package, @locale_dirs);

use Locale::TextDomain qw (my-package);

my $translated = __"Hello World!n";

my $alt = $__{"Hello World!n"};

my $alt2 = $__->{"Hello World!n"};

my @list = (N__"Hello", N__"World");

my @plurals = (N__ ("One world", "{num} worlds"),
N__ ("1 file", "%d files"));

my $question = __x ("Error reading file {file}: {err}",
file => $file, err => $!);

printf (__n ("one file read",
"%d files read",
$num_files),
$num_files);

print __nx ("one file read", "{num} files read", $num_files,
num => $num_files);

The module Locale::TextDomain(3pm) provides a high-level interface to Perl message translation.

Textdomains

When your request a translation for a given string, the system used in libintl-perl follows a standard strategy to find a suitable message catalog containing the translation: Unless you explicitely define a name for the message catalog, libintl-perl will assume that your catalog is called messages (unless you have changed the default value to something else via Locale::Messages(3pm), method textdomain()).
You might think that his default strategy leaves room for optimization and you are right. It would be a lot smarter if multiple software packages, all with their individual message catalogs, could be installed on one system, and it should also be possible that third-party components of your software (like Perl modules) can load their message catalogs, too, without interfering with yours.

The solution is clear, you have to assign a unique name to your message database, and you have to specify that name at run-time. That unique name is the so-called textdomain of your software package. The name is actually arbitrary but you should follow these best-practice guidelines to ensure maximum interoperability:

File System Safety

In practice, textdomains get mapped into file names, and you should therefore make sure that the textdomain you choose is a valid filename on every system that will run your software.

Case-sensitivity

Textdomains are always case-sensitive (i. e. Package and PACKAGE are not the same). However, since the message catalogs will be stored on file systems, that may or may not distinguish case when looking up file names, you should avoid potential conflicts here.

Textdomain Should Match CPAN Name

If your software is listed as a module on CPAN, you should simply choose the name on CPANS as your textdomain. The textdomain for libintl-perl is hence libintl-perl. But please replace all periods (.) in your package name with an underscore because ...

Internet Domain Names as a Fallback

... if your software is not a module listed on CPAN, as a last resort you should use the Java(tm) package scheme, i. e. choose an internet domain that you are owner of (or ask the owner of an internet domain) and concatenate your preferred textdomain with the reversed internet domain. Example: Your company runs the web-site www.foobar.org and is the owner of the domain foobar.org. The textdomain for your companys software barfoos should hence be org.foobar.barfoos.

If your software is likely to be installed in different versions on the same system, it is probably a good idea to append some version information to your textdomain.
Other systems are less strict with the naming scheme for textdomains but the phenomena known as Perl is actually a plethora of small, specialized modules and it is probably wisest to postulate some namespace model in order to avoid chaos.

Binding textdomains to directories

Once the system knows the textdomain of the message that you want to get translated into the users language, it still has to find the correct message catalog. By default, libintl-perl will look up the string in the translation database found in the directories /usr/share/locale and /usr/local/share/locale (in that order).

It is neither guaranteed that these directories exist on the target machine, nor can you be sure that the installation routine has write access to these locations. You can therefore instruct libintl-perl to search other directories prior to the default directories. Specifying a differnt search directory is called binding a textdomain to a directory.

Locale::TextDomain extends the default strategy by a Perl specific approach. Unless told otherwise, it will look for a directory LocaleData in every component found in the standard include path @INC and check for a database containing the message for your textdomain there. Example: If the path /usr/lib/perl/5.8.0/site_perl is in your @INC, you can install your translation files in /usr/lib/perl/5.8.0/site_perl/LocaleData, and they will be found at run-time.

Kate OS Live is a live CD edition of Kate OS 3.0 Beta which is now available for download and testing.
KateOS LIVE 3.0beta is now available. This version includes most of desktop applications and features Xfce as the graphical environment. It should be especially interesting for those who would like to help us in testing but do not have enough disk space.
The LIVE edition is a complete operating system with automatic hardware detection and auto-mount of all accessible partitions which will let you begin a fully effective work in just a few minutes.
Kate OS is a multitasking operating system which provides all that is necessary for programmers, webmasters, administrators and home users. The most important Kate OS features are high efficiency, safety, reliability and low system requirements. Kate OS provides full support for generally used multimedia.
Kate OS is a perfect combination of Linux power and utility. The complexity of installed software makes using the system comfortable, immediately after the installation process. Looking for a perfect solution for the experienced UNIX user? Kate OS is perhaps the best one.
Enhancements:
- The second beta of KateOS 3.6 is now available. It contains many changes, both important and purely cosmetic ones, such as: new update notifier; new 2.6.21.4 kernel; X.Org 7.2; the newest versions of KDE 3.5.7, GNOME 2.18.2 and Xfce 4.4.1, OpenOffice.org 2.2.0, and many more. The CORE edition also includes a partial French translation of the installer. The second beta also has a lot of bugs eliminated (including some in the KateOS LIVE installer). Everyone is invited to test and share the experience on the KateOS project forum.