Free knob software for linux

Lewin Pongs is an advanced game of pong.

An advanced game of pong with lots of options. A ball bounces around the screen and you hit it with paddles.

If you miss, your opponent scores, if your opponent misses, you score.

PONG, an adaptation of table tennis to the video screen, was the first commercially successful video game and is widely regarded as ushering in the video game era.

PONG was released by Atari on November 29, 1972.

PONG is a basic simulation of the racket sport of table tennis. A small square representing a ping pong ball travels across the screen in a linear trajectory. If the square strikes the perimeter of the playing field, or one of the simulated paddles, the square ricochets based on the angle of the impact.

Game play consists of players moving their respective paddles vertically to defend their scoring zones. Players score one point by maneuvering the square past their opponents paddle.

PONG can be played either by a single player pitted against a computerized opponent, or by two players each controlling a paddle. In Ataris original PONG arcade cabinets, players controlled their paddles using one of two small paddle controllers (a knob-like input device). Contrastingly, several of the derivative table tennis simulations employed longitudinally-sliding joysticks.

The volume normalizer plugin is an XMMS plugin that is used to give all songs the same volume level so that you wont need to play with the volume knob whenever a song changes.
Enhancements:
- Fixed build issues to make it build on x86-64 and detect missing xmms-devel files.

Jooky is an mp3 controller. I wrote it so that I can do any of:

Run it in the foreground in a curses screen.
Run it in the background and control it using itself as a client via tcp/ip from another host or the same host.
Run it from /etc/inittab and control it as above.
It also can play in random order (scramble).
The reason for the client/server is that I can now control it with LIRC. (Linux infrared control)

To run the command line based server, simply run jooky with no options in a terminal. Youll get an ncurses based screen interface to play with. The legend at the bottom will show you how to use it. It takes all of a minute to learn how to use it. If you know vi, then its even simpler. Any files that cant be played because there is no player for them, will be dimmer
than the others. Up and Down arrows are the same as j and k. Right and Left arrows adjust volume. Pgup and Pgdn take you up and down half a screen, as do capital J and capital K.

NEW! as of 0.96. "m" changes the Mixer knob, and right and left arrow adjust the current knob. Give it a try. aumix and read/write permission to /dev/mixer are required.

glFlow is a (D)DoS logger written with speed in mind. glFlow detects attacks on high speed links through real-time flow aggregation and analysis.
What do I run it on ?
It was written on FreeBSD and tested on both FreeBSD and Linux. It should work on any OS to which libpcap and OpenSSL were ported. The rest of the code is perfectly portable.
How does it work ?
Cisco Systems have defined the flow as a four value tuplet: {srcaddr, srcport, dstaddr, dstport}. The format evolved over time. The complete structures for various NetFlow versions are available on Ciscos site. Now, lets assume that the attacker floods the victim with packets that keep the same characteristics throughout the duration of the attack. No source spoof, no
source port increments or randomizations. That would lead to a very large packet rate inside that flow. glFlow calculates the average packet rate in every flow and raises an alarm signal if the threshold is hit.
What about spoofed attacks ? How are they detected ? Simple. glFlow keeps a history for every destination host that it sees. When a new flow is created, the flow counter for that host is incremented. The average number of newly created flows corresponding to a specific host in a specific amount of time is calculated, and, as above, an alarm is raised if the threshold is hit.
To prevent attacks that dont hit any of the above thresholds, theres
a new one starting with v0.1, measuring the packet rate for a destination.
Cant other tools, like SNORT, do this ?
We sincereley believe not. Remember, glFlow was written with high
speeds in mind. Weve been using it at over 500Mbps. At that speed, with an
ordinary x86 machine, even with a strong motherboard/NIC combination, you cant
do anything fancy. glFlow was specifically designed for detecting large floods
in real time, or at least something close to that.
How is it that its so fast ?
Well, Andrei did a great job implementing a very fast binary tree. That allowed us to drop the threaded model and choose a single loop design. The new results were stunning. The tests were made on a P4 Xeon/3 GHz, with an Intel GigE NIC. The average traffic rate was about 500Mbps, with an average packet rate of 100kpps. That lead to about 200k active flows. glFlow managed to clean the inactive ones in less than 0.3 seconds. There was no alarm raised
after more than 5 seconds of flooding. glFlow ate ~50% of the CPU, while consuming about 40MB of system memory.
How do I install and run it ?
Run ./configure --help. Youll see two adjustable knobs: --with-hash and --enable-debug. The first one permits you to switch between MD4 and MD5 summing of the flow and host structures kept in the memory. The second lets you run glflow in the foreground, printing some statistics on stdout.
The thresholds are harcoded in defs.h. You shouldnt have any trouble tweaking them. However, weve observed that the best results are obtained when using the same values for flow lifetime and the time between flow cleanups. And they shouldnt be much over 20. The smaller the tree is, the faster it will be cleaned.
Finally, edit your /etc/syslog.conf and write something like this: "local6.*< tabs >/var/log/something". Restart sys[k]logd afterwards.
Fire glFlow up, like this: "./glFlow < interface > < bpf filter >" and watch /var/log/something for changes. You may play with nmap or some DoS programs to test it. The IPs in the syslog will be shown as integers rather than in dotted notation. We decided to leave this job to the log analyzer.
Can it go even faster ?
Sure. There are a few methods which permit you to improve the packet capture. For more info read Luca Deris paper: http://luca.ntop.org/Ring.pdf
Enhancements:
- This is a bugfix release.

Volume.app is a small graphical software utility enabling quick and convenient control of a computers audio volume level. Volume.app is intended for use on Linux/Unix systems in conjunction with an X window manager that supports dockable applications ("dockapps") such as AfterStep, BlackBox, or Window Maker.

It is a refinement of an idea that first appeared in Timecops WMix: a user interface comprising a "knob" that can be interactively "turned" by clicking and dragging the mouse. I found this approach quite appealing, both from an aesthetic viewpoint, and (more importantly) from a user-interface perspective.

A handful of other dockapp volume control programs are out there, and I have tried many of them. An interface element present in most of these is some form of "slider" as the primary means of adjusting the volume. (A fictitious example may be seen at right). To my dismay, with this kind of interface, volume adjustments tended to be large and abrupt. Because the slider was so small, raising or lowering the volume "just a bit" required extremely careful control of the mouse-- a slip of the hand had the potential to spike the volume to full blast. (I have a set of Altec-Lansing ACS48 speakers which make this a rather unpleasant experience). This approach left much to be desired.

I longed for an alternative, and upon playing with WMix (pictured at left) I had found it. The knob was genius in that it provided a means of graphically adjusting the volume, as a slider would, without tying itself directly to the motion of the mouse. The basic mode of usage is identical: you click on the thing and drag the mouse up or down. However, with the knob, the range of motion need not be confined to the postage-stamp-sized area of the dockapp. The mouse travel needed to cover the entire range of volume settings can be made longer, on the order of the full height of the screen-- almost like a much larger, easier-to-use slider. No longer were precise movements needed to make volume adjustments!

Still, I found WMixs interface to be a bit busy (never was a fan of tiny little buttons) and the all-important knob was yet a rather small target to find with the mouse. So, I grabbed a copy of the WMix source code, and rebuilt it into a dockapp that had a much larger knob as its sole interface element. I dubbed it Volume.app, and have placed it here for the benefit of everyone.

Bookmarks Scrollbar is an extension which adds a scrollbar to the bookmarks menu.

A scrollbar is a graphical widget in a GUI with which continuous text, pictures or anything else can be scrolled including time in video applications, i.e., viewed even if it does not fit into the space in a computer display, window, or viewport.

Usually designed as a long rectangular area on one or two sides of the viewing area, containing a bar (or thumb) that can be dragged along a trough to move the body of the document as well as two arrows on either end for precise adjustments. The "thumb" has different names in different environments: on the Macintosh it is called a "thumb" on the Java platform it is called "thumb" or "knob"; Microsofts .NET documentation refers to it as "scroll box" or "scroll thumb"; in other environments it is called "elevator", "puck" or "wiper". Additional functions may be found, such as zooming in/out or various application-specific tools.

The thumb can also sometimes be adjusted by dragging its ends. In this case it would adjust both the position and the zooming of the document, where the size of the thumb represents the degree of zooming applied. A thumb that completely fills the trough, or "track" represents viewing the entire document, at which point the scrollbar may temporarily become hidden.

Unified Qmail Patch provides a concatenation of various patches.
Unified Qmail Patch is a concatenation of various patches for the qmail MTA. It supports SMTP AUTH after STARTTLS, Maildir++, regexp support in badmailfrom, and lots of features for high-end production servers.
Main features:
- Maildir++
- TLS encryption
- SMTP AUTH + SMTP AUTH close
- regexps in badmailfrom and support for badmailto
- external todo
- big remote concurrency patch
- external queue manager
- oversized dns responses
- reverse dns check
- tarpitting
- ESMTP size check from Gentoo
- tab bug fix in .qmail files
- linux link sync
- errno patch (compiles with gcc 3.x too)
- auth only after TLS patch from Gentoo
- Maildir quota fix patch from Gentoo
- qregex memleak fix patch from Gentoo
- David Phillips sendmail flagf patch
- Russ Nelsons QMTP patch for qmail-remote
- Jay Austads random qmqp pickup
- Alin-Adrian Antons integer overflow fix in qmail-smtpd.c
- Added support for SMTP throttling, using relayd
- Added my own patch, that checks whether the mail from value is different from the username used for SMTP AUTH, thus preventing source address spoofing. Useful for ISPs that only relay mails from authenticated users.
- The mail from verification is now configurable through a knob defined in /var/qmail/control/spoofcheck or in the environment variable $SPOOFCHECK
- It seems that in previous versions I accidentally ommited the support for a big todo, so heres a patch that finally supports it. My apologies to all :(