Free robin hood bbc software for linux

Xyria:DNSd is an high performance DNS server that supports only the most important features and resource records while being extremely fast and secure.
Xyria:DNSd peoject also supports round-robin load balancing.
Main features:
- extemely fast implementation (main target)
- very secure
- ip-address based listen()ing
- supporting IPv6 addresses and resource records
- load ballancing via round robbin
- running under an low-privileged UID & GID
- running under little endian systems: (at least) Linux, Solaris, OpenBSD
- nice configuration syntax/easy to configure
- DNSd able to forward querys
- DNSd can run as caching only-server
Enhancements:
- The database was modified. Now DNSd uses a hashed array of pointers to binary trees including single linked lists for double valued hashes.
- It sorts the zones (by TTL) by itself (the admin doesnt has to care in which order he has to place the zones in the config file).
- Some code cleanup and a small bugfix are also included.

LNX-BBC project is a mini Linux-distribution, small enough to fit on a CD-ROM that has been cut, pressed, or molded to the size and shape of a business card.
LNX-BBCs can be used to rescue ailing machines, perform intrusion post-mortems, act as a temporary workstation, and perform many other tasks that we havent yet imagined.
The LNX-BBC runs as a "live filesystem" CD. Nothing is installed, and the system returns to its previous OS once you pop the LNX-BBC out.
The LNX-BBC philosophy is "leave no trace". The LNX-BBC does not even mount your hard drives read-write.
To be a useful rescue system, it provides you with the tools to modify your hard drives. You must explicitly re-mount them read-write to take advantage of this.
We develop our own distribution specifically to fit in the space constraints of the tiny CD-ROMs. We compile everything from source code with -Os, and use an elaborate system of compression and pivot_rooting to make a 50MB CD-ROM hold all of the programs we include.
Enhancements:
- 2.4.19 kernel
- large IDE disk support
- more fonts
- more DHCP clients
- bittorrent
- bittorrent downloads of ISOs from the Web site
- bittorrent clients on the BBC
- coroners toolkit
- security upgrades
- openssh
- openssl
- new upstream versions of many software packages

SuperShaper-SOHO is a traffic shaping setup for DSL connections which prioritizes VoIP and interactive traffic and makes sure P2P traffic doesnt saturate your uplink.
IPCop 1.3 and newer is known to work and is the preferred deployment setup. Firstly, be sure to disable the integrated traffic shaper in IPCop 1.4 if you use SuperShaper-SOHO.

RT-Thread is a real-time operating system. It is designed specifically for small memory footprint platforms. The kernel supports the tranditional RTOS services, such as multiple threads, semaphores, mutexes, event flags, mailboxes, etc.
RT-Thread project also provides a C-expression interpreter shell, from which a programmer can access kernel variables and invoke system functions.
Main features:
Kernel Object System
- There is a kernel object system, which can access and manage all of the kernel objects. Kernel objects include most of the facilities in the kernel, for example, thread, semaphore etc. Kernel objects can be static objects, whose memory is allocated in compiling. It can be dynamic objects as well, whose memory is allocated from system heaps in runtime. Through the kernel object system, RT-Thread operating system can be independent from the memory management system and greatly enhance the scalability of the system.
Multi-Task/Thread Scheduling
- RT-Thread operating system supports multi-task systems, which are based on thread scheduling. The scheduling algorithm used in RT-Thread operating system is a full preemptive priority-based scheduling algorithm. It supports 256 priority levels, in which 0 is the highest and 255 the lowest. The 255th priority is used for idle thread. The scheduling algorithm also supports threads running at same priority level. The shared time-slice round-robin scheduling is used for this case. The time of scheduler to determine the next highest ready thread is determinant. The number of threads in the system is unlimited, only related with RAM.
Synchronization Mechanisms
- RT-Thread operating system supports the traditional semaphore and mutex. Mutex objects use inherited priority to prevent priority reversion. The semaphore release action is safe for interrupt service routine. Moreover, the block queue for thread to obtain semaphore or mutex can be sorted by priority or FIFO.
Inter-Thread Communication
- RT-Thread operating systems supports event/fast event, mail box and message queue. The event mechanism is used to awake a thead by setting one or more corresponding bit of a binary number when an event ocurs. The fast event supports event thread queue. Once a one bit event occurs, the corresponding blocked thread can be found out timing accurately, then will be waked up. In mailbox, a mail length is fixed to 4 byte, which is more effective than message queue. The send action for communication facilities is also safe for interrupt service routine.
Clock and Timer
- In default, the system uses clock tick to implement shared time-slice scheduling. The timing sensitivity of thread is implemented by timers. The timer can be set as one-shot or periodic timeout.
Memory Management
- RT-Thread operating system supports two types memory management: static memory pool management and dynamic memory heap management. The time to allocate a memory block from the memory pool is determinant and when the memory pool is empty, the allocated thread can be blocked (or immediately return, or waiting for sometime to return, which are determined by a timeout parameter). When other thread releases memory blocks to this memory pool, the blocked thread is wake up.
Enhancements:
- More porting was done to Samsung S3C44b0 CPU, AMTEL AT91SAM7S64, Nintendo DS, and Intel i386.

Protoscope is a utility that aids Web developers by revealing the HTTP communication in their own applications. It is a nice tool for Web developers who want to "look under the hood" as they develop.

Protoscope is somehow like a HTTP proxy serve and runs like it. It expects to receive HTTP requests from a Web client (such as your Web browser) that is configured to use a proxy.

Note: Most Web browsers allow you to conveniently select a proxy server to use, and the Protoscope Web site will eventually have instructions on how to achieve this for those who need assistance. If you write a HOWTO for configuring a particular browser to use Protoscope, I will gladly link to it. See http://shiflett.org/projects/protoscope/ for more information.

Protoscope forwards the HTTP requests to the origin server just as a proxy would and replies to the Web client with the servers responses. This is all transparent to the Web browser, and it does not affect your browsing in any way.

The difference is that Protoscope logs all communication in the log file that you configure it to use, so that you can examine this log file (or tail it) to examine the HTTP transactions.

In addition, version 0.7.1 added the option to have this information embedded into the HTML document itself. This makes debugging and related tasks extremely efficient while you are developing, and it can even help to avoid having to view source and risk the page being expired from cache or any other annoyances. Simply scroll to the bottom of the page anytime there is a question about the current
transaction. This is the recommended way to use Protoscope.

L4ip is a daemon that extends IPFilters simple round-robin L4 load balancing with health checks. It takes care of monitoring and dynamically adding and removing ipnat rules in the kernel.
L4ip fully supports UDP, TCP, and system()-style executions for health checks, including send/expect scripts, SSL connections, and much more.
Main features:
- Define as many clusters, with as many members as you need.
- Automatically adds and removes "ipnat" rules as needed.
- Flexible health check support, tcp-open, tcp-close, udp-open, udp-close, system.
- Simple scripting available for health checks in send/expect syntax with fnmatch pattern comparison
- Binary protocol supported in url-encoding style syntax (eg %0D)
- system() like execution of external commands available. (spawn your own health-check testers)
- Reload and restart leaving last-known-state available for less service impact.
- SSL supported for TCP testers.
- Optional IPF rules to sense RST return-packets for faster failure detection.
Enhancements:
- Solaris SMF example files were added along with a "proxy" command for protocols that need it, such as FTP and IPSec.

Xsnow application is the X-windows application that will let it snow on the root, in between and on windows.
Santa and his reindeer will complete your festive-season feeling.
How to compile:
To build:
xmkmf
make depend
make
To run:
./xsnow
or:
./xsnow& (in the background)
To install (be root):
make install
make install.man
If xmkmf does not work and you cannot get a working Makefile that way then try compiling yourself, eh, xsnow this way:
cc -o xsnow snow.c -lXext -lX11 -lXpm -lm -lsocket -lnsl
gcc, SUN Solaris users without a C-compiler, but with gcc installed, try the following two commands. The first compiles Xsnow, the second links Xsnow.
gcc -c -O2 -I/usr/openwin/include -DSVR4 -DSYSV xsnow.c
gcc -o xsnow xsnow.o -O2 -L/usr/openwin/lib -lXext -lX11 -lXpm -lm -lsocket -lnsl
Note: Xsnow-1.41 needs the Xpm library. It is available from:
ftp://ftp.x.org/contrib/libraries/
The current Xpm version is xpm3.4k
Enhancements:
- All you KDE-users can now be even happier with a KDE-enabled Xsnow 1.42!
- The snow will magnificently wipe out your icons, but not to worry, theyre not really gone.
- By wiping with a window or something you can make them reappear.
- Car owners are used to this for years. Thanks to Robin Hogan who figured this out for xpenguin.