Free configurator software for linux

Murrine Configurator provides the opportunity to configure all the Murrine Engine style options.

With Murrine Configurator i want to give users the opportunity to configure all the Murrine Engine style options.

The usage is very simple and the dialogs explain step by step the style options you can edit.

The program is written in bash and required only the installation of "zenity", that is a Gtk2 utility for bash scripting (if you are using ubuntu you can install it with "apt-get install zenity").

After the installation the program can be found under System -> Preferences -> Murrine Configurator.

Network Configurator is a network configuration tool.
Network Configurator is user-level tool that aims to make network configuration more easy. It have command line and GTK+ interface.
Supported network types:
- Ethernet
- PPPoE
- PPTP
- Wi-Fi (no WEP and WPA for now)
- dialup

/etc/net represents a new approach to Linux network configuration tasks. Inspired by the limitations of traditional configuration subsystems, /etc/net provides builtin support for configuration profiles, interface name management, removable device support, full iproute2 command set support, interface dependency resolution, and a QoS configuration framework.
/etc/net provides support for the following interface types: Ethernet, WiFi (WEP), IPv6/IPv6 tunnels, PSK IPSec tunnels, VLAN, PLIP, Ethernet bonding and bridging, traffic equalizer, Pent@NET, usbnet, and PPP. Due to its modular design, support for new interface types can be added without overall design changes.
Main features:
/etc/net provides builtin support for:
- configuration profiles
- interface name management
- removable devices
- full iproute2 command set
- interface dependencies resolution
- QoS configuration framework
- firewall support
/etc/net provides support for the following interface types:
- Ethernet
- WiFi (WEP)
- IPv4/IPv6 tunnels
- PSK IPSec tunnels
- VLAN
- PLIP
- Ethernet bonding and bridging
- traffic equalizer
- usbnet
- PPP (PPtP, PPPoE)
Enhancements:
- This release better matches the option set of /etc/net scripts 0.8.0.

PHP Big Brother Hosts Configurator (phpBBHC) is a collection of PHP scripts and one C program to configure hosts
for the Big Brother network monitoring software. It doesnt cover all the possible settings for Big Brothers hosts file but it should be enough for
most demands.

Ammendment: Big Brother has been pretty much replaced by Hobbit. I havent got around to using Hobbit yet but Ive heard its pretty backwards compatible with Big Brothers configuration and scripts. Ive heard of successful stories
of phpBBHC being used to configure Hobbit.

Welcome to bbconf, the all-in-one blackbox configuration tool. Never heard of blackbox before? Well, lets just say that its the best Window Manager for X thats out "there" in our humble opinion.

Simply put, this little utility here has such lofty goals as being the one place where you can configure anything and everything you need to that has to do with blackbox.

bbconf aims to do that through the use of plugins--plugins which allow you to configure anything you wish about blackbox or its helper applications such as bbkeys, bbpager, bbapm, bbmail, bbpal, etc.

bbconf is distributed with 4 plugins that allow you to configure blackboxs keybindings, blackboxs styles/themes, and your blackbox menus and submenus.

The architecture of the plugins themselves are very simple and elegant, thanks to xOrs work--making it easy for anyone else to add onto the distributed plugins to make it easy to configure whatever else you want to for your blackbox/X sessions.

bbconf has grown from two previous gui configuration tools, namely bbkeysconf (the gui blackbox keygrabber configurator) and toolbox (the gui blackbox style/theme editor).

But thanks to xOrs help, bbconf has become far more than the combination of those prior two tools. It has taken the place of them (read: no more development will be done on bbkeysconf or toolbox), and has the capability to do FAR much more.

bbconf is written in Qt and in some spots, uses raw Xlib functions to do what it needs to do. Qt Designer was used to help in laying out the forms and base classes--and makes the job of redesign/re-layout MUCH easier.

To run bbconf, youll need Qt libraries. If you want to compile bbconf by hand, youll need the Qt libraries, X libraries, X development packages and Qt development packages.

Log::Dispatch::Config is a Log4j for Perl.

SYNOPSIS

use Log::Dispatch::Config;
Log::Dispatch::Config->configure(/path/to/log.conf);

my $dispatcher = Log::Dispatch::Config->instance;
$dispatcher->debug(this is debug message);
$dispatcher->emergency(something *bad* happened!);

# automatic reloading conf file, when modified
Log::Dispatch::Config->configure_and_watch(/path/to/log.conf);

# or if you write your own config parser:
use Log::Dispatch::Configurator::XMLSimple;

my $config = Log::Dispatch::Configurator::XMLSimple->new(log.xml);
Log::Dispatch::Config->configure($config);

Log::Dispatch::Config is a subclass of Log::Dispatch and provides a way to configure Log::Dispatch object with configulation file (default, in AppConfig format). I mean, this is log4j for Perl, not with all API compatibility though.

METHOD

This module has a class method configure which parses config file for later creation of the Log::Dispatch::Config singleton instance. (Actual construction of the object is done in the first instance call).

So, what you should do is call configure method once in somewhere (like startup.pl in mod_perl), then you can get configured dispatcher instance via Log::Dispatch::Config->instance.

JVending project bridges P2P networks and wireless delivery of content to mobile devices. Due to high latency of wireless connections, it is not practical to directly hook up the mobile devices to the peer network, so I have taken a different approach with JVending.

A user sets up a personal provisioning server on their PC and hooks it into the network. Through the P2P network, we create a federation of provisioning servers. The mobile devices use the federated provisioning servers as content portals.

JVending differs from P2P systems, such as Gnutella or "Project JXTA" reference implementation, in the following ways. JVending provides:

1. Catalog management
2. Device detection, which delivers the appropriate content based upon the type of browser or device
3. Web based browsing of content, so you can share with your friends on a wired or wireless network, after you have already collected the content.
4. The ability to search for and distribute packaged archives on the peer network.
5. Web links tying together the network.
6. PPG integration for pushing content to mobile devices.

For 2005 - 2006, the major goals of JVending (roughly in order of importance) are:

1. Expanding P2P support, including more in the area of wireless messaging (SMS)
2. JSR-124 compliance
3. Performance testing and monitoring capability
4. Multimedia server and J2ME support. This covers full integration between the MMS Client and the provisioning server.

Setting up the Environment

Follow these steps:

1. Make sure that you have J2SE 1.4.2 JDK installed. If not, go to http://java.sun.com/j2se/1.4.2/download.html and download and install the JDK (not JRE). I have not tested with J2SE 1.5 JDK, so it may or may not work with that version.
2. Download the jvending-standalone.zip file from the JVending project site.
3. Unzip the file into a directory of your choice, say /jvending
4. Set the JAVA_HOME environmental variable, depending on your OS. In windows, you can do this through the Control Panel/System/Advanced/Environmental Variable: JAVA_HOME =
EXAMPLE: JAVA_HOME=c:Programsj2sdk1.4.2_06

Starting JVending

1. Go to the bin directory and click on the run.bat (for windows) or run.sh for Unix.
2. The first time you start JVending, you will see a JXTA Configurator screen show up. Type in your user name and password/verify password. Click OK.
3. Wait 10 seconds for JVending to finish its startup sequence and then go to http://localhost:80/jvending/login. If you get a 404 error, wait a few more seconds and try again. Login ID/Password: admin/admin. Click "Submit Query" button. You will now see the JVending home page.

Dolda Connect is a modular P2P filesharing client built around the Direct Connect model. It supports most of the latest features of the DC protocol.
It runs in client/server mode with a well defined protocol, allowing extensibility, flexibility, and multiple detachable user interfaces. Dolda Connect also has an optional multi-user mode.
For the average user, this yields two primary advantages:
- The daemon can be made to run on another computer, which can be on all the time (a server, if you will), while the user interface can run on the users workstation. That way, the user can turn off his workstation at night, while the server will continue all transfers in progress during that time.
- A user can control his daemon from another location, such as from work, school, a friend, etc.
This architecture also has many other advantages in store for the more advanced users; since the user interface communicates with the daemon using a well-defined protocol, other user interfaces can be written, such as an automatic downloader, a chatbot, etc. It is also designed for secure multiuser operation.
Enhancements:
- A GUI configurator tool was added.
- Portability issues were fixed so that it works on AMD64 now.
- The documentation was improved.
- The usual slew of minor bugs were fixed.