The C++ Portable Components currently consist of four libraries.
The Foundation library contains a platform abstraction layer
(including classes for multithreading, file system access, logging,
etc.), as well as a large number of useful utility classes, such
various stream buffer and stream classes, URI handling, and many
more. The remaining libraries include:
o Crypto - Encrypt/decrypt data or I/O streams
o Data - database access ODBC, SQLite, MySQL client
o Net - network classes (sockets, HTTP, etc.)
o NetSSL - SSL/TLS protocol sockets based on OpenSSL
o PageCompiler - C++ Server Page Compiler, for dynamic HTML in C++ apps
o XML - parser with SAX2 and DOM interfaces and an XMLWriter
o Util - config files and command line arguments, various utility classes
o Zip classes for (de)compressing data or I/O streams
This is now known as the '-all' distribution by the Poco project,
but the FreeBSD port remains named -ssl for hysterical raisins.
iMaze is a multi-player network action game for TCP/IP with 3D graphics
under X11 (XView, Motif or Athena). You run through a labyrinth and shoot
everything that is round without being hit by other round anythings.
Of course anything round is one of the following:
* other players playing over the net
* computer controlled ninjas
* deadly shots (except your own)
Features:
* sophisticated, reliable network protocol, works even with SLIP connections
via modem; modular, portable source code
* windows can be freely scaled to avoid speed drawbacks due to poor display
performance
* sound and joystick support
* scores; camera mode; labyrinth generator and interactive labyrinth editor
Audio support is somewhat flaky on FreeBSD (synchronization problems).
It works better with the old Voxware driver than with the current pcm driver.
The Independent JPEG Group's JPEG software
==========================================
This distribution contains the eighth public release of the Independent JPEG
Group's free JPEG software. You are welcome to redistribute this software and
to use it for any purpose, subject to the conditions under LEGAL ISSUES, below.
This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
and other members of the Independent JPEG Group.
IJG is not affiliated with the official ISO JPEG standards committee.
Includes EXIF patches from:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=106060
http://sylvana.net/jpegcrop/exifpatch.html
S10sh is a USB/serial userspace driver for the Canon PowerShot digital cameras.
Using S10sh you can download, upload and explore the images captured with your
PowerShot camera. The interface is quite similar to DOS's command.com.
S10sh supports the following PowerShot models:
G1 (works with USB, not reported if works with the serial interface)
G3 (from local patches, perhaps needs further testing/debug)
S10 (serial and USB)
S20 (serial and USB)
S100 aka Digital Ixus (USB only, since it lacks the serial interface)
A20 (needs testing)
A50 (serial only, supported with problems)
Pro70 (serial only, supported with problems)
Other models are reported to work as well: Elph S400, Digital Ixus V3, S30,
A60, EOS-10D.
With the release of libusb 0.1.3b (http://sourceforge.net/projects/libusb/),
S10sh gained USB support under FreeBSD.
The original author's web page is http://www.kyuzz.org/antirez/s10sh.html
I could not find a client with the features I was looking for, so yes,
here is yet another IRC client. Here's what makes it different from
others:
* absolutely NO scripting ability.
* termcap based (e.g. fast!).
* emacs-style key bindings
* full ircd 2.9+ support.
* virtual windows a la screen(1).
* multi server support.
* non blocking TCP connections.
* basic support for multi-homed systems.
* everything goes and stays in the lastlog.
* convenient scrolling (with searching abilities) in the lastlog.
* 10 display filters! (2 ignore features are based on this).
* highly customizable. (format strings, filters..)
* customization possible at every level (channel, window, server..).
* non blocking DNS lookups (A and PTR records).
* "tabkey" style completion for /msg, /squery and public discussion.
* DCC support.
* CTCP support.
-- Christophe Kalt <kalt@stealth.net>
"xtail" watches the growth of files. It's like running a "tail -f"
on a bunch of files at once.
You can specify both filenames and directories on the command line.
If you specify a directory, it watches all the files in that
directory. It will notice when new files are created (and start
watching them) or when old files are deleted (and stop watching
them).
This program is an oldie but goodie. It was posted to comp.sources.misc
in July 1989 (see ftp.uu.net:/usenet/comp.sources.misc/volume7/xtail.Z).
I remember posting an even earlier version to alt.sources. It has
been published in the O'Reilly & Associates "Unix Power Tools"
collection (book and CD-ROM). Over the years, some fly-by-night
organizations (such as the MIT X Consortium and SGI) have tried to
steal the "xtail" name. Don't be fooled! Insist on the original.
A huge compilation of Win32 codecs:
Video:
- Win32 VfW DLLs:
Indeo Video 3.2, 4.1
Microsoft MPEG-4 v1 & v2 beta
Microsoft MPEG-4 v3 ( also known as DivX ;-) )
Cinepak Video
ATI VCR-2
I263
Quicktime 6 (includes 3ivX, ZyGo)
Realplayer 9 (includes RV40)
xanim (includes 3ivX, Indeo3/4/5)
- Win32 DirectShow filters, decompression-only support:
Microsoft MPEG-4 v3 ( this decoder is slower than VfW one,
but offers wider range of picture control features )
Windows Media Video 7
Indeo Video 5.0
Motion JPEG ( using Morgan Multimedia shareware codec )
- Open-source plugins:
Motion JPEG ( using libjpeg, very slow )
Audio:
- Win32 ACM DLLs, decompression-only support:
Windows Media Audio ( also known as DivX ;-) Audio )
MS ADPCM
Intel Music Codec
- Open-source plugins, decompression-only support:
PCM
AC3
IMA ADPCM
MPEG Layer-1,2,3 ( compression into MP3 is also supported )
MSN Audio
GSM 6.1 Audio
- Win32 DirectShow filters, untested decompression-only support:
Voxware Metasound
ACELP.net
bgpq3 is a lightweight access-list/prefix-list/as-path access-list generator
for Cisco and Juniper routers.
This program is a mostly complete re-implementation of bgpq (net-mgmt/bgpq),
with next major advantages:
- much faster, especially for large as-sets.
- supports ipv6 both at transport level and in prefix/access-lists generation.
- supports asn32 in both asdot and asplain notation, also supports
"transition" as23456 generation instead of asn32.
However, bgpq3 can not be used as a full replacement of bgpq, because:
- "more specific" prefix filtering is not implemented (and not planned).
- GateD prefix-filters generation is not implemented (and not planned).
- Cisco standard access-lists generation is not implemented (and not planned).
- formatted output is not supported (yet?).
This package is a port of TAMU's extract program from NetLogger to look
at flow data instead of netlogger data. Blame Larry for it's faults, not
TAMU. Blame me for the FreeBSD port, not Larry :-)
If you don't already have a good guess what this program does and what
data it is looking for, the odds are that it isn't going to be of much
help to you. This program only works on Cisco flow data as captured
with Mark Fullmer's flowtools package. If you don't have that, get that
first, then look at this program.
In order for this to compile you will need flowtools from Mark
Fullmer's (net-mgmt/flow-tools port).
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.