Free rf modulator software for linux

Gizmo Daemon is the Linux Input Device Utility.
Ever want to make use of those keyboard keys and mouse buttons that X wont let you use? Ever want to quickly define a keyboard shortcut to do something like change or mute the volume? Ever want to use your joystick, second mouse, Griffin PowerMate, or any other random device you can think of to do fun things like control applications, switch desktops, switch tracks in XMMS / BMP, launch programs, or do pretty much anything else you can think of?
Are you a MythTV user? Got an RF or IR (LIRC) Remote? Annoyed with how frustrating it is to map keys, or is the remote super touchy? Would you like a simple easy way to configure your remote, and have it function properly at the same time? Want to have different key maps based on what application is currently being used?
Gizmo Daemon does all of that, and more! Gizmo Daemon operates on a fairly simple philosophy: let the user decide. Any and all device events are sent to the configuration scripts, and from there the user can decide what should be done with those events. A number of functions are exposed to the scripts which allows the script to interact with any of the loaded device plugins in any way desired.
Main features:
- Control any application with any device
- Utilize those special keys on your fancy keyboard, even if your X server or terminal doesnt support them! Now you can actually make the volume controls change the volume, or the media buttons control XMMS / BMP! Set the buttons to launch your favorite programs, switch virtual desktops, or run whatever application you want!
- Give per application key mappings, very handy for remote users!
- Fix touchy remotes by removing quick duplicate keystrokes
- Control system mixer volume
- Change virtual desktops (only for EWMH capable window managers)
- Launch programs
- Send keyboard and mouse events to applications
- Send device events from one device to another, or create fake device events (control a mouse cursor with a joystick, or keyboard)
- Visualization of system events such as CPU USage, and XMMS / BMP sound output on visual devices (such as the LED on the Griffin PowerMate USB Dial).
- Fancy on screen displays via XOSD. Now your workstation or MythTV box can have nice TV friendly volume displays controlled by your remote!
- And more! Anything you can think of is probably possible
Enhancements:
- Add Powermate setRotateSensitivity function
- New variable in GizmoDeviceStrings.py called
POWERMATE_ROTATE_SENSITIVITY for this!
- Add PowermateEvent ClickTime property (duration of button press)
- Add GizmodThread class for creating threads from Python
- DO NOT USE!! (HIGHLY EXPERIMENTAL!)
- Add GizmodTimer class for creating timer objects from Python
- Add script 200-Powermate-ButtonTimeout for generating button
timeout events
- New variable in GizmoDeviceStrings.py called
POWERMATE_BUTTON_TIMEOUT for this!
- Add script 201-Powermate-Beryl
- So far this detects a powermate button timeout and
unfolds the beryl cube, and lets you scroll the unfolded
cube with the dial
- Add base script GizmoScriptAltTabber so that devices have an
easy way of sending Alt-Tab events
- New variable in GizmoDeviceStrings.py called
ALT_TAB_TIMEOUT for this!
- Add remote ?00-Intercept scripts for alt-tabbing support
- This allows the default mapping to start alt-tab
and to still alt-tab passed applications (if alt-tab
actually focuses apps) if those apps happen to use
the same button that initialized the alt-tab
- Add Gizmod namespace to libGizmod

FancyLauncher is basically a program launcher with many customizable features. The snapshot shows how it looks like with the default configuration. The rxvt button is focused and the associated tooltip is displayed.
The license is GPL. This is the new version of the former E-FancyLauncher, written for enlightenment as an epplet. For people migrating to FancyLauncher the utility EF2F is provided to translate the E-FancyLauncher configuration file to the FancyLauncher configuration file. If you use it, you should have a look at the default configuration and the plugins directory to see the new features.
The configuration directory is located in your home directory and is named .FancyLauncher. There you will find the configuration file config and you should copy the plugins with the command cp -r /usr/local/FancyLauncher/plugins ~/.FancyLauncher/.
The configuration file works by definitions.
- common defines common options that are inherited by all the buttons. These options can be redefined.
- button defines a button launcher.
- digital_clock defines a digital clock.
Enhancements:
- Suggestions: adding dir asked by dmitry kirsanov and appending files by Marc A. Tamsky,
- pretty printing of played time asked by Chris Bidmead, and printing of songs length asked by Draco Paladin.
- Added +file to add files or directories.
- Added -file to remove files or directories.
- Added color printing (use more or less -Rf to view HELP).
- Added an emacs transcriber from Chris Bidmead.
- Added print, a general printing function (deprecates all other printing commands).
- Fixed memory leaks.
- Renamed sample scripts with the .sh suffix.
- Added conditional print (eq,neq).
- Added uniq command to remove duplicates from the playlist.
- Added the sample script playlist2html.sh to demonstrate the print command.
- Added clear to clear the playlist.

BashBot project is a fork of bbots by Dave Crouse. Its an IRC bot written in BASH. In the days between writing that ntcpclient and the official bbots release, I had been playing with it for a few days (gave me an excuse to see what I could do with bash.
This is more here in case anyone is curious (i.e. want to compare it to crouses) I wouldnt actually recommend using it because I discovered a potential security hole.

The Problem: If you get the bot to expand a variable, which has a control character in it, such as * or ` it can cause problems, because it gets expanded by the shell. You can hence do "!tell someone foo *" and it would send

PRIVMSG someone : foo < LIST OF FILES IN CURRENT DIRECTORY >

Which is obviously a hazard. I would imagine it would be pretty bad if you started playing with `rm -rf /` or something.

This seems to be something I introduced by having it expand the line when passing to the modules. This was to try and avoid having to do the string tokenisation in the modules themselves, hence allowing me to remove a lot of code.

PL/1 for GCC project is an attempt to create a native PL/I compiler using the GNU Compiler Collection. PL/I is a third-generation procedural language suitable for a wide range of applications including system software, graphics, simulation, text processing, Web, and business applications.
This is the eleventh code drop of the GCC front-end for the PL/I programming language.
PL/I for GCC is released under the terms of the GNU Public License; version 2. Version 0.0.11, includes a new infrastructure for the PL/I preprocessor.
It has been more than a year since the previous release of pl1gcc, but development has picked up again, so expect releases to happen more frequently. And remember you are always welcome to join the project, we need really help at all levels of development.
The v0.0.11 release marks another important step forward towards a fully functioning PL/I compiler: the preprocessor. The current implementation supports just a few statements, but thanks to the tools flex and bison, it is straight forward to add the missing preprocessor statements. Expect a few new ones to be added with each new release, just like the PL/I parser has been developed.
Currently there is still no codegeneration taking place, so dont run out and uninstall your production PL/I compiler, just yet.
But read ahead for some good news.
It would still be a great help for us if you try the compiler on some of your own source code, or if you could construct a PL/I program that really tests the corners of the grammar. Basically a program that does all what the syntax allows. As inspiration, have a look at the test program written by Paul Karagianis
http://www.multicians.org/proc-proc.html
but I am sure you can create a much worse PL/I program, which we would like to see. And if you release it under GPL it can be added to the pl1gcc hall of fame, so just go ahead and do the coding.
Please inform us about any syntax errors that might occur so we can check if the error is in the pl1gcc parser, and not in your code.
Installation:
Since the GCC PL/I is not yet part of mainline GCC, there are some manual steps you have to perform before you can use the GCC PL/I compiler.
If you are using Cygwin under Windows, please follow the instructions in the file INSTALL.cygwin. If you want to use eclipse please consult INSTALL.eclipse.
First you need the source code for the GCC compiler itself. If you do not already have the sourcecode installed you will have to download it.
This is how we did it; you can probably come up with another way.
Get latest working version of the gcc-core-4.2-2006mmdd weekly snapshot and
the latest version of the pl1gcc-0.0.x archive file, from http://pl1gcc.sourceforge.net
Note: The snapshot of gcc downloaded from the pl1gcc project is known to work with pl1gcc. If you try another snapshot from the GCC project, please let us know if it works or not.
GCC recommends to separate the source directories from the build directories, so create a direcory to hold the unpacked source code.
cd ~
mkdir gcc-src
Unpack the downloaded gcc-core-4.2-2006mmdd snapshot into your directory for gcc source, assuming the downloaded files are stored in ~/download, this will unpack the gcc compiler file:
cd ~/gcc-src
tar -xjf ~/download/gcc-core-4.2-2006mmdd.tar.bz2
Note: this will create a directory named ~/gcc-src/gcc-4.2-2006mmdd
Unpack the pl1gcc-0.0.x.zip file into your home directory, with these commands
cd ~
unzip ~/download/pl1gcc-0.0.x.zip
This will create the directories ~/pl1gcc-0.0.x/pl1
Create a link from ~/gcc-src/gcc-4.2-2006mmdd to your unpacked pl1 library:
cd ~/gcc-src/gcc-4.2-2006mmdd/gcc
ln -s ~/pl1gcc-0.0.x/pl1 pl1
Create an empty ~/gcc directory, where the built object will created:
cd ~
rm -rf ~/gcc
mkdir gcc
Unpacking is now done, and you can start to build your downloaded compiler. This might take a while (*).
Now do:
cd ~/gcc
../gcc-src/gcc-4.2-2006mmdd/configure
make
and go enjoy some of your favorite bewerages, and of course dont forget to make a donation to the pl1gcc project.
You can speed up the compilation considerably, by disabling some of the languages you do no longer need, now you have PL/I as your favorite compiler.
To do this edit the files ~/gcc-src/gcc-4.2-2006mmdd/ /config-lang.in,
and set the variable
build_by_default="no"
Enhancements:
- This release adds support for using the tilde character as the "not" operator and support for ENVIRONMENT().
- It adds location information to most messages. %INCLUDE can now have filenames inside of quotes.

ETrace is a configurable static port network tracing tool, similar to traceroute, but supporting ICMP, TCP, UDP and other IP protocols.

Usage:

etrace [ -BbCcnv ] [ -p profile ] [ -F config ] [ -i interface ] [ -I icmp-type ] [ -T port ] [ -U port ] [ -P protocol ] [ -r probe-count ] [ -t timeout ] [ -1 hop ] [ -h hop ] [ -m hop ] [ -A address ] [ -s port ] [ -f flags ] [ -d data ] [ -D data-file ] [ -R count ] [ -q seq] [ -w window ] target [...]

Options:

etrace has a wealth of options ranging in function from controlling output to the detailed construction of trace packets.

Profile Options:

A profile is a pre-configured list of options stored in a shared, or user specific configuration file. By defining profiles, complex etrace option sets can be easily accessed with a single command line option.

-p, --profile
Specify a profile.
-C, --clear
Clear the current list of probes. This option can be used to allow a profile to inherit options from another profile, but specify its own list of probes.
-F, --config
Specify an alternative profiles file.

Interface options

-i, --interface
Specify interface. If unspecified, etrace will examine the routing table and select the most appropriate interface for each target address.
-c, --promisc
Put in interface into promiscuous mode. As this option increases the load on the system in general, it should only be used if spoofing of source packets address is enabled with the "-A" option.
Trace Type Options
-I, --icmp
Specify an ICMP trace and the packet type to use. ICMP traces may use Echo (E or P), Timestamp (T or S), Netmask (N or M) or Info (I). The default trace probe is an ICMP Echo.
-h, --hop
Specify a specific hop to investigate.
-m, --maximum
Specify the maximum number of hops.
-r, --probes
Set the maximum number of probes to send per hop. The default is 3.
-t, --timeout
Set the maximum amount of time, in milli-seconds, to wait for a response to a probe. The default is 3000 (three seconds).

Packet Construction Options

-A, --address
Specify the source IP address of generated packets.
-s, --source
Set the source port of the generated probe packets. If unspecified, etrace uses a random high port.
-f, --flags
Specify TCP and/or IP flags. Takes a comma delimitered list of any of the following flags: RF, DF, MF, FIN, SYN, RST, PSH, ACK, URG, ECE, CWR (Default: SYN)
-d, --data
Specify the data content of generated probe packets. Standard meta-characters are recognised (e.g. "nt") as are binary values given in octal (e.g. " 00x00");
-D, --data-file
Load the data content of the generated probe packets from the specified file. Filenames beginning with @ a loaded from the etrace shared data directory (usually /usr/local/share/etrace). etrace currently ships with the following predfined packet data files: dns, ike.
-R, --random
Fill the data content of the generated probe packets with the specified number of random bytes.
-b, --badcksum
Generate and send probe packets with bad checksums.
-q, --seq
Specify the TCP sequence number.
-w, --window
Specify the TCP window size.

Output Options

-v, --verbose
Increase output verbosity.
-B, --debug
Enable debugging output.
-n, --numeric
Disable name resolution.

Examples:

etrace www.sample.com

Launches a trace ICMP Echo, the default, trace to www.sample.com. Specifiying the options "-I E" whould accomplish the same results.

etrace -T 80 www.sample.com

Similar to the previous example, except the trace is performed on TCP port 80.

etrace --udp 53 --data-file @dns ns.sample.com

Starts are trace to ns.sample.com on UDP port 53 with the trace packets containing data loaded from the file /usr/local/share/etrace/dns (a file supplied with etrace that contains a simple dns request to resolve 127.0.0.1).

etrace -p dns -p fast ns.sample.com

The default profiles shipped with etrace include "dns" (which equates to the options shown in the previous example) and "fast" (which decreases both timeouts and the number of probes sent for each hop, as well as disabling name resolution). Profiles are stackable, with latter options overriding those specified in earlier profiles.

The syncopt script and its associated work practices are yet another approach to the standard sysadmin problem of keeping multiple machines software installations up to date.
It is independent of the vendors packaging scheme and thus you can use either your vendors system or syncopt, or both!
The core notion is that the install is done once on a central machine and then syncopt takes care of attaching that to every client, often via cron.
- easy to use
- flexible enough to permit control of what is installed locally on a machine and what is served remotely from a central server (for disc space or other reasons)
- keep out of the way of the ``vendors namespace, to avoid treading on the vendors install and conversely to protect our additions from damage by vendor upgrades and patches.
Main features:
lightweight
- If a package is not to be installed local to a client then the burden is usually just two symlinks on the client.
optional
- You can install packages with syncopt or with the vendors packaging scheme, or both!
permits trial installs
- Under syncopt you can install multiple versions of the same package for trial or legacy purposes.
centralised
- The default package version is controlled by a symlink on the master host; change that and all the clients will follow suit next time they run syncopt.
customisable
- Clients can control which packages are local and also override which version is their default for a given package.
Using
Local Package Install
As a consequence, to make an instance of something local to a client machine (lets call it pkg, release version), remove the local symlink:
$ rm /opt/pkg-version
Make a stub directory:
$ mkdir /opt/pkg-version
Alternatively, just edit the .syncopt file and add this line:
pkg-version local
Run syncopt:
$ syncopt -x
That syncs everything. You can just do the new package like this:
$ syncopt -x pkg pkg-version
which syncs the generic (unversioned) link and the version specific local directory.
Undoing a Local Package Install
To make a once-local copy remote, remove the local copy:
$ rm -rf /opt/pkg-version
Also, if you edited the .syncopt file as above, remove that line.
Run syncopt:
$ syncopt -x pkg pkg-version
Bringing a Client into Sync after a New Package Install
To set up a new clients /opt directory after a fresh install:
$ mkdir /opt # if necessary
$ syncopt -x
/opt/.syncopt
The behaviour deduced from the presence or absence of a directory can be overridden with the /opt/.syncopt file, which contains line of the form:
pkg version
to make version the default package version on this particular machine, or
pkg local
to force a package to be local on this machine, or
pkg-version local
to make a particular version local, or
pkg nosync
to not run syncopt on it at all.

libdbf is a C-library for reading dbase files.

dBASE Converter is a command line tool to show and convert the content of dBASE III, IV, and 5.0 files.

dBASE Converter project reads dBASE databases and prints the content to the screen or converts it to CSV files or SQL instruction sets.

It reads xBASE-compatible databases and prints the content to the screen or converts it to comma-separated (*.csv) files which can be opened in Excel, StarOffice, and most other spread sheets. It can also be used to show some statistics about the content.

NOTES

If you have problems to build your own binary of libdbf, please read the following.

Error Message:
Cant locate object method "path" via package "Request"
at /usr/share/autoconf/Autom4te/C4che.pm line 69

Solution:
Execute the command
rm -rf autom4te.cache/
in the libdbf directory and run autogen.sh again.