Search Results for "install with"

Kashyyyk is full featured, open source, cross platform IRC client. It was originally written to replace HexChat on OS X. At the time, HexChat (a fork of XChat) had only had a single release on OS X, which was still in alpha. Kashyyyk is extremely small, the binaries and related libraries totaling around half a megabyte. Kashyyyk also has very few external dependencies, the official binaries statically linking all supporting libraries. Kashyyyk is natively available for OS X, Windows,...

Play now at http://webchat.freenode.net/?channels=#twentyonebot. Just say "Hi!" This bot will play the game of 21 with users in an IRC chat room. The game is quite similar to Blackjack, but is played with dice instead of playing cards. Players continue rolling dice until the sum of all rolls is as close to 21 as possible, but don't go over! This project is based off of the source for the same game which was written by Jason Hamilton and updated slightly more recently by LuizCB (aka pincel).

A plugin for Winamp which allows song change events to be forwarded to Snarl. To install, copy the gen_snarl.dll file, which can be found in the files section here, to C:\Program Files\Winamp\Plugins (default path for Winamp installations) and res

Telnetchatd is a chatserver which uses the telnetprotocol. Users do not need to install a client, as every desktop-OS comes with a preinstalled telnetclient. Programmed in pure C, the server needs very little resources and runs on any unix-like system.

Rhino is a fast, light weight and high performance ircd. A system administrator can install this package on a unix like system and configure the server with easy clean configuration files.

...It was forked from the now unmaintained dircproxy. It does/will support: bouncing, flexible logging, DCC connections, ipv6, ssl, multiple users and multiple servers. Easy to install and easy to use.

...;P note that we don't use for /etc/ax25/axports -at all- and think it should disappear as it makes no sense to have callsigns and mtu's and stuff on an interface, in a config file, AND in a program. whatever info is needed should just be obtained from the interface. like with any other protocol stack (you also don't have to put your ip address in your webbrowser, a seperate file in /etc, and the interface) (so there is also no need to install those old ax25-tools - just the kernel suffices)