Dbmail is the name of a group of programs that enable the possibility of
storing and retrieving mail messages from a database (currently MySQL,
PostgreSQL or SQLite).
* Scalability.
Dbmail is as scalable as the database system that is used for the mail
storage. In theory millions of accounts can be managed using dbmail. One
could, for example, run 4 different servers with the pop3 daemon each
connecting to the same database (cluster) server.
* Manageability.
Dbmail is based upon a database. Dbmail can be managed by changing settings
in the database (f.e. using PHP/Perl/SQL), without needing shell access.
* Speed.
Dbmail uses very efficient, database specific queries for retrieving mail
information. This is much faster then parsing a filesystem.
* Security.
Dbmail has got nothing to do with the filesystem or interaction with other
programs in the Unix environment which need special permissions. Dbmail is
as secure as the database it's based upon.
* Flexibility.
Changes on a Dbmail system (adding of users, changing passwords etc.) are
effective immediately.
exmh is a TCL/TK based interface to the MH mail system. It provides
the usual layer on top of MH commands, as well as many other features:
MIME support! Displays richtext and enriched directly.
Color feedback in the scan listing.
A colour coded folder display with one label per folder.
Smart scan caching. News read/post. koi8-r support.
Facesaver bitmap display. Ispell support.
Background inc. You can set exmh to run inc periodically.
Searching over folder listing and message body.
A dialog-box interface to MH pick.
An editor with emacs-like bindings and MIME support.
Glimpse interface. You can index all your mail with glimpse
and search for messages by content.
User preferences. You can tune exmh through a dialog box.
User hacking support. A user library of TCL routines is supported.
IMPORTANT: exmh depends on the TK send facility for its background
processing. With TK 3.3, send now uses xauthority mechanisms by default,
unless you compile TK with -DTK_NO_SECURITY. Generally, this means that
you **MUST** must run xdm to start your Xserver.
CVC3 is an automatic theorem prover for Satisfiability Modulo Theories (SMT)
problems. It can be used to prove the validity (or, dually, the
satisfiability) of first-order formulas in a large number of built-in logical
theories and their combination.
CVC3 is the last offspring of a series of popular SMT provers, which originated
at Stanford University with the SVC system. In particular, it builds on the
code base of CVC Lite, its most recent predecessor. Its high level design
follows that of the Sammy prover.
CVC3 works with a version of first-order logic with polymorphic types and has
a wide variety of features including:
* several built-in base theories: rational and integer linear arithmetic,
arrays, tuples, records, inductive data types, bit vectors, and equality
over uninterpreted function symbols;
* support for quantifiers;
* an interactive text-based interface;
* a rich C and C++ API for embedding in other systems;
* proof and model generation abilities;
* predicate subtyping;
* essentially no limit on its use for research or commercial purposes
(see license).
ndiff is a utility for comparing putatively similar files, ignoring small
numeric differences. The utility is written by Nelson H. F. Beebe and
covered by the GNU General Public License (GPL), version 2. It may be
built with arbitrary precision support (more powerful) or using built-in
floating point precision, see Makefile.
Assessing the consistency of a numerical program run in multiple
environments (operating systems, architectures, or compilers) can be a
difficult task for a human, as small differences in numerical output values
are expected. File differencing utilites, such as diff(1), will generally
produce voluminous output, often longer than the original files.
ndiff solves this problem. Taking two text files expected to be
identical, or at least numerically similar, it allows to specify absolute
and/or relative error tolerances for differences between numerical values
in the two files, and then reports only the lines with values exceeding
those tolerances. It also tells by how much they differ. A simple example:
% ndiff --relative-error 1.0e-3 test019.txt.1 test019.txt.2
### Maximum relative error in matching lines = 8.64e-51 at line 129 field 4
Book of Psalms from the Douai Bible (1610) in fortune(6) file format
In general, taking random out-of-context verses from a Bible is a
VERY bad idea. This said, this is an experiment to generate a not
too bad fortune-cookie database under the following principles:
- Only the text from the psalms, which are usually meant for praying,
were taken.
- The texts always include at least some context: you are always
notified where the text came from and there is always sufficient
text so that the phrases make sense.
- The text was taken from the classic Douai Bible, a direct translation
from the latin Vulgata. The old language will not give you false
impressions that you are actually understanding it fully.
- No effort was done to remove the original comments. Non-Christians
may rightfully feel the translation is biased.
This is meant to be a general aid for Christian meditation: it is not
generally to be taken as my message-of-the-day from God.
To use, you need UNIX fortune(6) utility and you should follow the
instructions from the corresponding man page.
[ excerpt from developer's site ]
It is a free library for decoding mpeg-2 and mpeg-1 video
streams. The main goals in libmpeg2 development are:
Conformance - libmpeg2 is able to decode all mpeg streams that
conform to certain restrictions: "constrained parameters" for
mpeg-1, and "main profile" for mpeg-2. In practice, this is what
most people are using. For streams that follow these restrictions,
we believe libmpeg2 is 100% conformant to the mpeg standards - and
we have a pretty extensive test suite to check this.
Speed - for most current systems, the display will actually take
more time than the mpeg-2 decoding. For systems that have hardware
color conversion and scaling (as we can use with the xv extension
in Xfree 4), you should be able to watch DVD streams on a Celeron
400. On a PIII/666 with null display you should get about 110 frames
per second.
Portability - most of the code is written in C, and when we use
platform-specific optimizations we always have a generic C routine
to fall back on.
Radiator is a highly configurable and flexible Radius server that supports
authentication by a huge range of authentication methods such as Flat files,
DBM files, Unix password files, SQL databases, remote Radius servers
(proxying), external programs, NT User Manager, Active Directory, LDAP, PAM,
iPASS, GRIC, NIS+, Tacacs+, a wide range of ISP billing packages such as
Emerald, Platypus, Rodopi, Hawk-i, Interbiller98, Freeside etc, your legacy
user database etc, etc.
Radiator now supports more 802.1x secure wireless and LAN authentication
methods than any other Radius server giving a wide choice of 802.1x network
clients.
Radiator also includes many features not found in other Radius servers such
as double-login prevention, username rewriting, full vendor-specific
attributes, time-of-day blocking and a GUI for running user tests. Full list
of technical features.
Runs on all Unix, Linux, Windows 95, 98, NT, 2000, Mac OS-9 and Mac OS-X, VMS.
Due to license restrictions, this package must be purchased and manually
downloaded from the Open System Consultants web site.
If you have an AT&T Wireless, Bell Canada/Bell Mobility, Cellular One,
Cingular, Cricket, Sprint PCS, SkyTel, or T-Mobile cell phone or pager, and you
want the ability to send SMS messages to it via a command-line utility, this is
what you need. All this program requires is a computer with a baseline Perl 5.x
installation and web access. NO EXTRA PERL MODULES REQUIRED!
How does it work?
SendSMS connects to your service provider's web page and pretends to submit a
form to their 'Instant Messaging' web page. Currently, AT&T Wireless, Bell
Canada/Bell Mobility, Cellular One, Cingular, Cricket, SkyTel, Sprint PCS, and
T-Mobile are supported. Users are encouraged to modify the provided templates to
add support for any providers who are currently unsupported.
Other Service Providers
If you are interested in supporting another service provider please try to
modify sendSMS on your own. It is not hard at all. Instructions and examples are
included in the code, and if you're familiar with the site you're porting to, it
takes about 15 minutes. If you get sendSMS working with any other providers' web
sites, please email Paul Kreiner [deacon at thedeacon.org] and/or the port
maintainer a patch so it can be added to the next release.
Preppy is ReportLab's templating system. It was developed in late 2000 and has
been in continual production use since then. It is open source (BSD-license).
The key features are:
- *small*. Preppy is a single Python module. If you want a templating system
'in the box', it's easy to include it in your project
- *easy to learn*. It takes about one minute to scan all the features
- *just Python*. We have not invented another language, and if you want to do
something - includes, quoting, filters - you just use Python
- *compiled to bytecode*: a .prep file gets compiled to a Python function in
a .pyc file
- *easy to debug*: preppy generates proper Python exceptions, with the correct
line numbers for the .prep file. You can follow tracebacks from Python
script to Preppy template and back, through multiple includes
- *easy to type and read*. We've been using ``{{this}}`` syntax since well
before Django was thought of
- *8-bit safe*: it makes no assumption that you are generating markup and does
nothing unexpected with whitespace; you could use it to generate images or
binary files if you wanted to.
The snow package provides support for simple parallel computing on a
network of workstations using R. A master R process calls makeCluster
to start a cluster of worker processes; the master process then uses
functions such as clusterCall and clusterApply to execute R code on
the worker processes and collect and return the results on the master.
This framework supports many forms of "embarrassingly parallel"
computations.
Snow can use one of four communications mechanisms: sockets, PVM, MPI,
or NetWorkSpaces (NWS). NWS support was provided by Steve Weston.
PVM clusters use the rpvm package; MPI clusters use package Rmpi; NWS
clusters use package nws. If pvm is used, then pvm must be started,
either using a pvm console (e.g the pvm text console or the graphical
xpvm console, both available with pvm) or from R using functions
provided by rpvm. Similarly, LAM-MPI must be started, e.g. using
lamboot, for MPI clusters that use Rmpi and LAM-MPI. If NWS is used,
the NetWorkSpaces server must be running. SOCK clusters are the
easiest approach for using snow on a single multi-core computer as
they require no additional software.