esniff (formerly dbsniff) is a very basic set of tools useful for network traffic analysis and scripting across machines. It consists of three tools: esniff, nwait/npush, and loss_chk/loss_srv. esniff is a packet sniffer based on pcap that does certain things like traffic summaries (not better but hopefully easier than tcpdump). nwait and npush implement the DOS "pause" command working over the network. loss_chk and loss_srv are for checking the loss rate of a line.
how dare you?
... speak against the long-time-tested, proven-to-be-working, widespread-and-commonly-adopted, holy gnu autoconf-tools? EVERYONE uses them!
well, everyone but me. I tried to write some configure script for my little project, thinking "you managed everything so far, this cannot truly be too hard".
I spent two - fully wasted - days looking for documentation, trying to write makefile.am, configure.in, what.ever, then trying to copy someone else's, and finally stuck to my old hand-written shell script which compiles. gradually I upgraded this to a little bigger shell script, which is capable of recompiling itself. dependancies? it's my project. it runs on my machines.
well, I like makefiles, I like configure-based projects, because of the advantages mentioned. but writing one is - at least - a pain in the ass. we definitely need something new, so that someone like me - someone programming on a little application - is able to make it public in a simple way without one year developers work to write an install script.
In my personal view of the matter could we have many, many more programs or developers if there were a more simply way of spreading your application. I can write programs, but I cannot create a configure script. thats not how it should be, in my view.