Free to run or not to run software for linux

run in xterm is an servcie menu which adds "run in xterm" & "run in xterm as root" to action menu on binary files, scripts etc.

It has 2 languages: english and polish.

Installation:

copy/save this file in
~/.kde/share/apps/konqueror/servicemenus

Run a web server inside LAN is a simple script to run a WWW server inside a Local Area Network. Run a web server inside LAN script assume all iptables features are compiled statically in the kernel, or all modules are loaded.

Otherwise you may encounter some surprises trying to utilize the more featureful and creative commandlines that Ive come up with.

Sample:

#external and internal interfaces
EXT=eth0
INT=eth1

# clear everything, and create my cascading chains
iptables -F
iptables -N e0
iptables -N tcpin
iptables -N udpin

# e0 is the name of our chain for eth0
iptables -I INPUT -i $EXT -j e0

# OUTPUT Chain
iptables -A OUTPUT -o $EXT -j DROP -p icmp --icmp-type ! echo-request

# remote gnutella queries were really pissing me off one day
# iptables -A OUTPUT -o $EXT -j DROP -p tcp ! --syn --dport 6346
# iptables -A OUTPUT -o $EXT -j DROP -p tcp ! --syn --sport 6346

# $EXT Chain
# a single rule to accept SYN Packets for multiple ports (up to 15)
iptables -A tcpin -j ACCEPT -p tcp --syn -m multiport --destination-ports 873,993,995,143,80,113,21,22,23,25,53

# stateful connection tracking is wonderful stuff
# ESTABLISHED tcp connections are let through
# If we send a SYN out, the ACK is seen as RELATED
# then further communication is accepted by the ESTABLISHED rule
iptables -A e0 -j ACCEPT -m state --state ESTABLISHED
iptables -A e0 -j ACCEPT -m state --state RELATED

# certain ports I simply DROP
iptables -A tcpin -j DROP -p tcp --syn -m multiport --destination-ports 6346,139

# UDP rules...
iptables -A udpin -j DROP -p udp -m multiport --destination-ports 137,27960

# I run a DNS server, so we must accept UDP packets on port 53
iptables -A udpin -j ACCEPT -p udp -m state --state NEW --destination-port 53

# lets log NEW udp packets on ports 1024:65535, then let them through
iptables -A udpin -j LOG -p udp -m state --state NEW --destination-port 1024:65535 --log-level debug --log-prefix UDPNEW --log-ip-options
iptables -A udpin -j ACCEPT -p udp -m state --state NEW --destination-port 1024:65535

# lets log NEW tcp packets on ports 1024:65535, then let them through
iptables -A tcpin -j LOG -p tcp --syn --destination-port 1024:65535 --log-level debug --log-prefix TCPNEW --log-tcp-options --log-ip-options
iptables -A tcpin -j ACCEPT -p tcp --syn --destination-port 1024:65535

# lets log INVALID or NEW tcp packets on priveleged ports, then DROP
# (remember I have certain ACCEPT rules higher up the chain)
iptables -A tcpin -j LOG -p tcp -m state --state INVALID,NEW --destination-port 1:1023 --log-level warn --log-prefix TCPPRIV --log-tcp-options --log-ip-options
iptables -A tcpin -j DROP -p tcp -m state --state INVALID,NEW --destination-port 1:1023

iptables -A e0 -p tcp -j tcpin
iptables -A e0 -p udp -j udpin
iptables -A e0 -j LOG --log-level debug --log-prefix NETFILTER --log-ip-options -m state --state INVALID,NEW
iptables -A e0 -j DROP

# NAT Rules
# I run a web server inside...
iptables -t nat -A PREROUTING -p tcp -i eth0 --dport 80 -j DNAT --to-destination 192.168.1.4:80

Damn Small Linux Not is built on Damn Small Linux technology. Damn Small Linux Not is also small, bigger than DSL but smaller than most. Damn Small Linux Not provides a reliable, and compact array of applications based mostly on the GTK2 libraries.
DSL-N is not an evolution of DSL, it is not intended as progress over the philosophy of DSL, but is intended for a different user, or the same user under different circumstances.
Main features:
- it is small
- it has software which is feature full
- it takes advantage of redundant lib dependencies and suits to pack features into a tight distribution
- DSL-N has a modern kernel and does not squeeze out critical modules that would limit compatibility
Like DSL, DSL-n can:
- Boot from from a CD as a live Linux distribution (LiveCD)
- Boot from a USB pen drive
- Boot from within a host operating system (thats right, it can run *inside* Windows)
- Run very nicely from an IDE Compact Flash drive via a method we call "frugal install"
- Transform into a Debian OS with a traditional hard drive install
- Run fully in RAM
- Modularly grow -- DSL-N is highly extendable without the need to customize
- The applications in DSL-N were chosen because they are functional, usable, and relatively compact. Unlike DSL, DSL-N has GTK2 applications, that means DSL-N will need more ram and CPU cycles than DSL. To have a pleasant experience, we recommend at least 64MBs and 300MHz.
DSL-N, unlike DSL, does not have a hard size cap, but it is being developed by the DSL team, and we hate bloat! So, dont expect DSL-N to get too big.
Why are you making this offshoot of DSL when DSL is so successful? Because a 50MB, GTK2 based distribution, with a 2.6.x kernel and excellent hardware detection/support is a contradiction in terms. DSL-N represents our best effort to stay compact while providing for the needs of those who want the Bling Bling such as SATA support, Gnumeric, Abiword, gMplayer.
Enhancements:
- Added "noprompt noeject" to default boot options for frugal installs.
- Fixed madwifi wireless.
- Fixed chpasswd vs passwd. "secure" boot option now works correctly.
- Added gnu-utils into the base iso.
- Fixed USB2 not loading bug
- Improved mydsl=hdxy when specified to not also search this makes it consistent with restore boot option.
- Enhanced exitcheck to prompt warning if no backup device is selected when requested to save special settings.
- Fixed multi user hard drive install bug.
- Added murgaLua Lua/Fltk development toolkit.

Robo Hunt is an action game where you have to run for life and plutonium.

Take all plutonium and dont be caught. The robot hunters are smart and they do not cheat.

TorK project is a Tor Controller for KDE.

TorK allows you to configure, run and update Tor. It also allows you to view the Tor network and choose how you would like to interact with the network.

TorK is very much in an alpha state.

Python in Scheme is a scheme library that allows you to run Python code within Scheme.

Python in Scheme project uses the Python/C API to embed a Python interpreter.

Bio::Tools::Run::PiseWorkflow is a class to create a Pise workflow using Pise application objects as methods. A workflow is defined by a set of methods which all instanciate the class PiseApplication.

SYNOPSIS

# First, create a Bio::Tools::Run::AnalysisFactory::Pise object:
my $factory = new Bio::Tools::Run::AnalysisFactory::Pise();
# Then create the application objects (Pise::Run::Tools::PiseApplication):
my $clustalw = $factory->program(clustalw);
$clustalw->infile($my_alignment_file);
my $protpars = $factory->program(protpars);

# You can specify different servers for different applications :
my $protdist = $factory->program(protpars
-remote => http://kun.homelinux.com/cgi-bin/Pise/5.a//protpars.pl,
-email => your_email);

# Create a new workflow object :
my $workflow = Bio::Tools::Run::PiseWorkflow->new();

# Define the workflows methods using the application objects:
# the application method $protpars will receive the output of
# type readseq_ok_alig from the application method $clustalw.
$workflow->addpipe(-method => $clustalw,
-tomethod => $protpars,
-pipetype => readseq_ok_alig);

# The application method $clustalw will be piped to a second
# application method ($protdist) using the output of type readseq_ok_alig.
$workflow->addpipe(-method => $clustalw,
-tomethod => $protdist,
-pipetype => readseq_ok_alig);

# The application method $protpars will be piped to the application
# method $consense using the output of type phylip_tree.
my $consense = $factory->program(consense);
$workflow->addpipe(-method => $protpars,
-tomethod => $consense,
-pipetype => phylip_tree);

# Run the workflow.
$workflow->run();

Traffic Prioritizer is designed to run on a Linux router and prioritize users traffic by their bandwidth consumption.

It is aimed to shape the "bandwidth greedy" clients (P2P, YouTube, IPTV, etc.) so that the ones who are just browsing do not lack bandwidth.