MoinMoin is a Python clone of WikiWiki, which is a composition system;
it's a discussion medium; it's a repository; it's a mail system;
it's a tool for collaboration.
Use of bzip2, which is intended to replace bzip, is recommended.
The algorithms used in bzip2 are different and incompatible with
those used in bzip. To open .bz archives, you must use bzip, and
to open .bz2 archives you must use bzip2. Although bzip2 sometimes
yields slightly larger output, it is faster, more reliable, maintained,
much more widely used and is believed to be patent-free.
Julian Seward, the author of bzip, gives this warning:
This program may or may not infringe certain US patents
pertaining to arithmetic coding and to the block-sorting
transformation itself. Opinions differ as to the precise
legal status of some of the algorithms used. Nevertheless,
you should be aware that commercial use of this program
could render you liable to unfriendly legal action.
AnyEvent::DNS::EtcHosts AnyEvent::DNS behavior to use /etc/hosts
The DNS lookups are emulated. This resolver returns the standard DNS reply based
on /etc/hosts file rather than real DNS.
You can choose different file by changing PERL_ANYEVENT_HOSTS
environment variable.
This module also disables original AnyEvent::Socket's helper function
which reads /etc/hosts file after DNS entry was not found.
It prevents to read this file twice.
The AnyEvent::Socket resolver searches IPv4 and IPv6 addresses separately.
If you don't want to check the addresses in DNS, both IPv4 and IPv6 addresses
should be placed in /etc/hosts or the protocol family should be set explicitly
for resolve_sockaddr function.
LLDP (Link Layer Discovery Protocol) is an industry standard protocol
designed to supplant proprietary Link-Layer protocols such as
Extreme's EDP (Extreme Discovery Protocol) and CDP (Cisco Discovery
Protocol). The goal of LLDP is to provide an inter-vendor compatible
mechanism to deliver Link-Layer notifications to adjacent network
devices.
lldpd implements both reception and sending. It also implements an
SNMP subagent for net-snmp to get local and remote LLDP
information. The LLDP MIB is partially implemented but the most useful
tables are here. lldpd also partially implements LLDP-MED.
lldpd supports bridge, vlan and bonding. Bonding need to be done on
real physical devices, not on bridges, vlans, etc. However, vlans can
be mapped on the bonding device. You can bridge vlan but not add vlans
on bridges. More complex setups may give false results.
ctrace is an IPv4 traceroute tool that supports many features missing
in standard 4.3BSD traceroute(8). It is programmed entirely in perl.
The primary difference between ctrace and other traceroute tools is
its ability to trace routes in multiple protocols. ctrace also has
some additional nifty features:
* Automatic round-trip-time (RTT) averaging, which makes output
cleaner and more intelligible.
* One or more packets can be launched per TTL/hop. By way of contrast,
4.3BSD traceroute(8) forces at least two. This capability makes
ctrace faster.
* 4.3BSD traceroute(8) emulation in most output, so it will hook in to
existing parsers.
* The ability to skip an arbitrary number of hops, saving you time
that would be normally wasted tracerouting your own network.
* Fine-grained control over trace packet headers, assisting in
bypassing burdensome packet filters.
This package contains the URI.pm module with friends. The module
implements the URI class. Objects of this class represent Uniform
Resource Identifier (URI) references as specified in RFC 2396 and
updated by RFC 2732. Release 1.50 includes the initial attempt at
providing support to IRIs. URI objects now support the 'as_iri'
and 'ihost' methods.
URI objects can be used to access and manipulate the various
components that make up these strings. There are also methods to
combine URIs in various ways.
The URI class replaces the URI::URL class that used to be distributed
with libwww-perl. This package contains an emulation of the old
URI::URL interface. The emulated URI::URL implements both the old and
the new interface.
NNTPCache is Squid for news (plus lots more).
NNTPCache (very efficiently, using shared memory, COW, mmaps, etc)
executes on the localhost pretending to be an NNRP news reading
server. In fact, what it does is pass certain NNTP commands through
to real (remote and possibly local) news-servers based on various
pattern matching rules. nntpcache then takes the output from those
servers and caches & indexes it in funky ways (much specific case
magic goes into this). The next time such information is asked
for, or other information which can be logically inferred from the
previously collated information, it is sent directly from the cache,
without consulting the remote servers. NNTPCache can transparently
merge multiple servers, (permiting local newsgroups with remote
NNTP feeds), filter articles, xovers, and headers based on weighted
regular expressions, and has built in NoCem/PGP (anti-spam) support
(see http://www.nocem.org/ for details).
FisicaLab (can be pronounced as PhysicsLab) is an educational application to
solve physics problems. Its main objective is let the user to focus in physics
concepts, leaving aside the mathematical details (FisicaLab take care of them).
This allows the user to become familiar with the physical concepts without
running the risk of getting lost in mathematical details. And so, when the user
gain confidence in applying physical concepts, will be better prepared to solve
the problems by hand (with pen and paper). The latest release of FisicaLab have
the following modules:
- Kinematics of particles 2D.
- Circular kinematics of particles 2D.
- Static of particles 2D.
- Static of rigid bodies 2D.
- Dynamics of particles 2D.
- Circular dynamics of particles 2D.
- Heat, calorimetry, ideal gas and expansion.
The standard distribution of Apache does not provide adequate means for user
tracking, and this module provides them. What it actually does:
+ if the user has provided the cookie header with the correct cookie-name,
the module writes this cookie in notes with the name uid_got (accordingly,
then it may be written to the log);
+ if the user has arrived without the required cookie, the module issues the
SetCookie header for him/her and writes the cookie thus issued in notes
with the name uid_set (and this may also be written to the log);
+ if built-in P3P support is included, the P3P header is also issued as the
Set-Cookie header is issued.
The Andika font is designed to work on systems and with applications that
provide support for TrueType fonts and for Unicode character encoding.
This includes Microsoft Windows 9x or greater, as well as recent versions
of the Mac OS (version 9.0 and later), and also some implementations of
Unix / Linux (TrueType font support on Unix and Linux may depend upon the
particular applications in use). On some systems (true, at least, of
32-bit Windows), it can also be used with older applications that use
legacy, industry-standard, 8-bit character encodings.
The preceding characterization of system requirements describes the
minimum needed to display characters. Realizing the full capabilities of
this font involves additional requirements. This font is designed to work
with either of two advanced font technologies, Graphite or OpenType.
To take advantage of the advanced typographic capabilities of this font,
you must be using applications that provide an adequate level of support
for Graphite and OpenType.