Free powerdns daemon 2.9.21 software for linux

The PXE daemon allows network managers to boot PXE-enabled machines over the network. Basically it envolves BOOTP, TFTP (so far so good) and a PXE daemon. This is where all the trouble starts. There is only one implementation arround, and if doesnt work on anything other than little endian machines.
I originally tried to correct some of the major problems in this code. However firstly, I could not find anyone with at Red Hat or Intel to deal with and secondly, Intel seem very unintrested in porting the code the big endian machines. The source is also very messy and it would have taken longer to correct the original code, than to re-write the whole daemon. If you dont believe me on this point, just have a look at it, IMHO any daemon that responds to keyboard input is a bad thing (it thinks it had packets coming from the keyboard even when in daemon mode)
You are lucky then, but a lot of places have already got a bootserver, and most likely it will be a UNIX based machine that is not x86. So, why put in another machine when there is already one there?
If you know enough about PC, you will know there are several operating modes. The mode the PC boots in is only able to access the low 640KB of memory. By using the PXELINUX bootstrap code it is possible to boot using the full amount to memory in the system. The means you can do some nice things including boot a Linux kernel + Ramdisk over the network, as you would for a Sun. Please note that the Intel bootstraping code is very limited in this sense.
I dont recommend it anymore, I just havent had time to do a lot of updates, PXELINUX is far far better (see link below). However Intels PXE daemon is naff (IMHO)
Enhancements:
- Increase the interface buffer to hold more than three interfaces
- Fixed a segfault in when multicast was disabled
- Fixed null pointer dereference when looking at interfaces with no IP address

OLSR daemon project is an implementation of the Optimized Link State Routing protocol for mobile ad-hoc networks (MANETs).
OLSR is a routing protocol for mobile ad-hoc networks. The protocol is pro-active, table driven and utilizes a technique called multipoint relaying for message flooding. olsrd also implements a popular optional link quality extension. Currently the implementation compiles on GNU/Linux, Windows, OS X, FreeBSD and NetBSD systems.
Olsrd is ment to be a well structured and well coded implementation that should be easy to maintain, expand and port to other platforms. The implementation is RFC3626 compliant with respect to both core and auxiliary functioning.
Olsrd supports use of loadable plugins. These can be used to to handle and generate custom packettypes to be carried by OLSRs MPR flooding scheme or for any other desired functioning.
Enhancements:
- Network simulator (olsr_switch) added. Read more in the README file included in the release.
- New experimental fish eye link distribution algorithm. Read more in the README file included in the release.
- Tiny Application Server(TAS) plugin added
- Plugin interface changes. Olsrd now exports all symbols mening that plugins can access all olsrd functions easily.
- Olsrd now builds and runs on OpenBSD
- Build system rewrites(OS detection is now done automagically)
- Lots of bugfixes and minor changes

PowerDNS project has developed a complete suite of technologies surrounding Internet Naming and email.
Internet Naming is at the core of all online activities and is involved in each and every transaction on the net. Email remains the killer application of the Internet.
Enhancements:
- This release contains two important security fixes, which should also solve the very rare reports of stability problems.
- Additionally, a new class of misconfigured domains will now always be resolved correctly, instead of intermittently.

LIRC Client Daemon project is an attempt to solve certain problems in LIRC.

The LIRC Client Daemon is a per-user daemon that sits between the LIRC daemon (from the Linux InfraRed Control project) and any other programs that use LIRC.

It ships with a replacement library for LIRCs liblirc_client, which connects to lirccd instead of lircd. This primarily helps solve the synchronization present in the standard liblirc_client, and also empowers the user with a much more flexible configuration file format.

Password Manager Daemon is a daemon that serves data to application via a socket. The data is stored in an encrypted XML file. A work in progress.

PyMusicD is yet another jukebox daemon written in python. It was born out of my frustration with the current mp3 jukeboxes, mostly the lack of features that I want. Ive also been playing with python quite a lot lately, and this is my first attempt at a large project in python.
The player is being written to satisfy my own requirements for a car mp3 player, although theres no reason you couldnt use this for a home mp3 player, or work mp3 player.
It assumes that your network users are (mostly) benign, and doesnt take a lot of precautions against malicious users who want to screw with your mp3s. Take appropriate measures to only allow trusted users to play with it, at least until I secure it a bit better.
Its primary purpose is to run in the background, and play mp3s whenever they are in the playlist.
Usage
Unpack this to its own directory. Edit the pymusicd.conf file to your liking. Run python PyMusicD, then run python pymusic to play around with it. The client operates very similarly to most shells, and includes tab completion for commands (but not arguments... yet.)
If you wish to install this to the system, you may do so by running python setup.py install. This will install the server binary in the default place for your platform (according to distutils.) You may then edit the config file (/etc/pymusicd.conf by default) and run the server by running PyMusicD. The cli client will be named pymusic.
This software is currently in development. It is not ready for end users yet. You should have familiarity with scripting in python before you set about to use this software. That being said, if you find bugs that arent listed in TODO, and/or have problems with the software that arent listed in TODO, email me (zwhite@darkstar.frop.org) and Ill see what I can do to help you. Code patches/suggestions are always welcome.
This is known to work on my Slackware 9.0 machine using the Python 2.2.2 package that came with it. I have also tested it on my Mac OSX 10.2.8 machine with Python 2.2. I have no reason to believe that it wont work on any machine with a Python 2.x interpreter and
either mpg123 or mpg321. Your mileage may vary. If it doesnt work on your platform, please let me know. My goal is to have this work on any platform that python runs on.
Enhancements:
- Fixed a bug when adding an entire directory with %2A instead of *
- Added a debug command to get server state, currently only playstatus is reported, will add more as needed.
- Changed the way the stop command works to eliminate a bug.
- Check to make sure a file exists before we add it to the playlist.
- We no longer start playing music as soon as the playlist has entries.
- Instead, we wait for a play command to be issued.
- Added config file support. Defaults to /etc/pymusicd.conf or ./pymusicd.conf
- Added a setup.py and setup.cfg file. Now users can install PyMusicD using the standard "python setup.py install" method that other scripts and modules use.

CPQ Array Daemon project keeps on monitoring your controller and checks for abnormal conditions. By default is only reports to the syslogs, but you can make it send SNMP Traps to selected hosts.

This tool can run on a linux based intel box with a smart array controller from Compaq. It reports status changes in the disks both to the syslog and to a snmp trap host.

The default is to only log to the syslog. You can specify traphosts with the -t parameter at the commandline. Multiple traphosts are allowed. It checks for valid input, but any errors are non-fatal, in fact the traphost is just ignored..

To ensure correct opereration compile it for the same kernel that runs on the machine where you want to use this. At least make sure that the version of the SmartArray driver is the same. Strange things can happen otherwise.

Installation:

The simplest way to compile this package is:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.