Free others know what software for linux

Know Base project consists of knowledge, document, and project management tool.

Know Base is a Web-based knowledge management system. It allows users to share files and projects across multiple business divisions.

A unique notification system alerts users when projects are modified, or when new projects are added that match their search terms.

CPAN::Test::Others is a Perl module to include tests for other modules on CPAN.

SYNOPSIS

You dont have any use for this module, just run its tests and report them to CPAN Testers

Sometimes I have an urge to write tests for other modules. Getting these tests included in the real distributin is not always easy, other module authors are busy too. They might have a real life.

So this module does not have its own code, it only has prerequisites and tests for those other modules.

Sablotron is a fast, compact and portable XML toolkit implementing XSLT 1.0, DOM Level2 and XPath 1.0. Sablotron is an open project; other users and developers are encouraged to use it or to help us testing or improving it.

Sablotron is written in C++ and we try to keep it as portable as possible. Click here here to see Sablotron cross-reference sources. We compile Sablotron on Linux (using g++) and Windows 2000 (using MS Visual C++).

GA does not directly support other platforms but as far as we know, it runs on Solaris, FreeBSD, OpenBSD, HP-UX, Irix and all Win32 systems. It should be possible to port Sablotron on other systems as well. In the event you run any other port of Sablotron, please let us know.

Docker is a docking application (WindowMaker dock app) which acts as a system tray for KDE and GNOME2. Docker can be used to replace the panel in either environment, allowing you to have a system tray w ithout running the KDE/GNOME panel or environment.

I wrote and designed Docker to work with Openbox 2, but it should work fine in any window manager that supports WindowMaker dock apps.

If you running WindowMaker or otherwise and experiencing problems, you should try using the -wmaker option to make docker keep a fixed size.

Docker requires a KDE3 compliant window manager to handle KDE3 system tray icons, and since it is a docking application, the window manager needs to also support WindowMaker Dock Apps. The only window manager that meets these requirements to my knowledge is:

- Openbox 2 (http://icculus.org/openbox)

If you know of any other window managers that support the KDE3 hints for the system tray and docking apps (i.e. that docker works in), please let me know so I can add them to this list, and test docker out in them!

Why dont my GNOME2 system tray icons show up?

I dont know! Email me and let me know what application isnt working. (Dont you dare email me about a GNOME1 application!

Porsche Gemballa is a KDM theme featuring a Porsche Gemballa. Let me know if you like it!

License: You are free to use for personal use. Do not distribute. Do not link directly to the file. All links must point to http://www.knightechnologysolutions.com/downloads/ For any use other than Private/home use, please include this copyright notice.

The SlotSig library is a library that provides type-safe connections between C++ classes.
When programming in C, its usual to use callback functions (moreover when you do GUI stuffs). In C++, we prefer to encapsulate things into classes, and usually we want a rather type-safety.
This small library attempt to provide an easy-to-use, type-safe, C++-friendly solution to the problem. The idea is to define slots, either as global functions or member methods, that will be called when some signals are emitted The signals and slots do not need to really know about each other, only a pointer and a compatible signature is required.
Inconsistent connections (when return type or parameters do not match) should be detected at compile-time.
If youve heard about the Qt, libsigc++, Sigslot or boost libraries, or any other Im not aware of (if this is the case, let me know !), maybe you wonder why yet another signals lib. Here are the main reasons :
- Qts system needs a preprocessor (called moc, for Meta-Object Compiler) that will produce additionnal code to enable the connections and handle the signal emitting ; its quite simple to use, but you cant use templates on signal/slot-enabled classes, and inconsistencies are not detected at compile time but at runtime ;
- I found libsig++ a great thing, but a little bit to complex to use, and I dislike some casts done into it ; I also dislike the fact that a function (or method) connected twice will be called twice when emitting the signal ;
- Boost is fine, but to use the signals module you also need a rather large part of the whole lib ; theres nothing really wrong with that, I just wanted something smaller â and easier to use ;
- It was fun to code, and because I did it, I find SlotSig the simplest signal/slot library available.
Enhancements:
- Incorporated the Makefile from Leopold Palomo-Avellaneda, to generate a global shared library containing the very small amount of static code.
- Updated benchmarks. The 1.x versions of SlotSig will remain binary-compatible. No major new feature is expected, mainly cosmetic changes and bugfixes. The main line of development will be done in a 1.99.x branch, maybe leading someday to a 2.0 version.

gozerplugs 0.9.0.17 is professionally designed as a plugin package for gozerbot. gozerbot is the Python IRC bot and Jabber bot in one.

In an effort to be able to play Halo 2 with some out of state friends, I wrote an xbox system link proxy that would essentially bridge only xbox network traffic across across layer 3 networks using UDP.

Written in C and uses libpcap and libnet. A later update added multicast support so Apples Rendezvous (mdns) protocol could span subnets and networks.

xboxproxy project a very simple program that simple takes certain packets and forwards them to other known xbox proxies.

The xbox system link bridge will let you essentially bridge the broadcast and multicast traffic across multiple networks using these proxy bridge-points.

The xbox system link uses ethernet addresses (Layer 2) to indicate destination address and UDP (Layer 4) to send data. If you arent familiar with the OSI model, then the layer information wont help you here. Basically, the 3 layers we care about for this system link proxy are ethernet (layer 2) and udp (layer 4). Theres a special mention for the ip layer (layer 3) but that will be explained shortly.

System link packets come in two flavors: broadcast and unicast. In Halo 2, when you go to look for system link games, your xbox will send ethernet broadcast packets probing for available games.

Broadcast packets are received by every network device on your layer 2 segment, this usually means your subnet or immediate network. Other xbox systems who are hosting games will respond directly to your xbox using your xboxs ethernet address (MAC address) as the destination.

This process is called "discovery." After the discovery process completes and your xbox knows about other xboxes hosting games on the network, it begins direct communication to the known xboxes. When you try to join a game, your xbox sends packets directly to the other xbox you are connecting to. Direct communication continues until you quit the game.

A special note needs to be made, becuase you cant simple skip over layer 3 (the ip layer). We know now that addressed communication uses ethernet addresses, and we also know that the payloads are inside UDP packets, but what about the IP layer?

The IP layer has addresses of its own, among other kinds of flags. Xboxes use the IP of 0.0.0.1 to communicate. This is nothing *too* special, but if you want to sniff only your xboxs traffic, then you can simply filter for that ip and youll get it.

The proxy works by listening for broadcast packets from any xboxes on the immediate network. Any broadcast packets are forwarded to any known proxies over UDP. The proxy also keeps track of ethernet addresses by proxy. So if a packet from "my" xbox wants to talk to another xbox, the proxy will know which proxy that target xbox is on, and only forward the packet to that proxy.

This is a very simple system, and I dont have to know anything about the system link protocol beyond what the underlying layers are used for communication.
I later did some investigating into iTunes music shares. iTunes uses mdns (Apple calls it Rendezvous) for "discovery" of other iTunes music shares.

The discovery is done over a protocol called multicast. Adding mdns support to the proxy/bridge program was quite trivial, and I have tested that it does in-fact work. You can use it to listen to iTunes music shares which are not on your immediate network.