Free designed 2b sweet software for linux

renameit is an MP3 filename standardizer. It formats your MP3 filenames based on the ID3 tag info, removes embedded spaces, and notifies you when an MP3 has no ID3 tag.

This is an example for usage:
Some Song from some album.mp3 with ID3 Artist of "Some Dudez" and ID3 Trackname of "Some Song" ends up beingSome_Song(Some_Dudez).mp3

./addtag FileToBeTagged.mp3
It will prompt you for artist and track name, add the tag, and then move
the file up to the mp3s directory, where you can run renameit on it.

./batchrenameit
It will get all the mp3 filenames in top directory, and call renameit for
each.

./edittag FileToBeEdited.mp3
Displays current ID3 tag and prompts for edit. After edit, calls
renameit.

./batchtag
Mass file tagger. Gets all mp3 filenames in need_id3 directory and calls
addtag for each.

./batchtagedit
It will get all the mp3 filenames in this directory tree, and call edittag
for each. Great for adjusting things like bands named Perl Jam..altho that
might be a kewl name for a band ;)

./makeindexfile
This builds index.html for all mp3 files in this directory tree. The
index will only show the mp3 files.

Sopeq is a stealth ingress and egress filtering firewall for IPTables with an easy to configure rules file.
Sopeq project can be used to configure even the slightest details of IPTables with just a minor change in the rules file.
Sopeq can be used to configure even the slightest details of IPTables with just a minor change in the rules file.
Argument Descriptions:
accept/droplog/rejectlog/log - This specifies what to do if a packet matches the
criteria given. "accept" accepts the packet, "droplog" drops and logs
the packet with given "lbl" variable (see section "vars" below),
"rejectlog" rejects and logs the packet with given "lbl" variable, and
"log" ONLY logs the packet with given "lbl" variable. Hmmm, I think I
see an eerie pattern emerging here...
if - This specifies what network interface the packet is travelling over.
This can also match packets NOT travelling over an interface by simply
adding an exclamation mark [!] before it. There should NOT be a space
after the exclamation mark like iptables requires.
in/out - This specifies whether the rule is looking at packets coming in or
packets going out. "in" should be used for most server rules, and
"out" should be used for most application rules. The rule is made by
adding the appropriate INPUT and OUTPUT rules in iptables to accept the
response to the packet as well.
This field can be left blank, but only if the "ports" field is blank as
well. This type of rule would allow all packets from a specific IP or
something to that extent.
tcp/udp/icmp - This is pretty self explanatory, it specifies the protocol of a
packet, IE: TCP, UDP, or ICMP. You can leave this blank to match all
protocols.
IPs - This specifies what specific IP addresses to allow for the rules. You
can leave this field blank to match all IPs. You can specify multiple
IP addresses by separating them with a comma, and/or use IP ranges.
Two methods of IP ranges are supported. The "1.2.3.0/24" method and
the "1.2.3.4-1.2.3.10" method. You can combine IPs and IP ranges in
the same rule with the comma delimeter.
Examples:
1.2.3.4
11.22.33.0/24
123.45.67.3-123.45.67.90
1.2.3.4,5.6.7.8,11.22.33.0/24,123.45.67.3-123.45.67.90
ports - This specifies which ports to allow on. Multiple ports can be
specified by separating them with a comma. If you leave the field
blank, it allows on all ports.
extras - This specifies extra options added onto the end of the rule. The field
is divided into two sections with a "|", which separates the extras for
the INPUT table with the extras from the OUTPUT table (in that order).
In order to have a space in the extras, you have to put the whole thing
in quotes (currently, you can only use double quotes, not single
quotes). These extras are just standard iptables options, so if you
want a list, view the iptables manual.
Examples:
No extras for the INPUT rule, "-m owner --uid-owner 0" for the
OUTPUT rule:
"|-m owner --uid-owner 0"
No extras for the INPUT rule, "-m owner --cmd-owner httpd" for the
OUTPUT rule:
"|-m owner --cmd-owner httpd"
vars - The syntax of a var field is:
varname="value"
Enhancements:
- The "version" option was added.
- A minor alteration was done in the way iptables was called.
- Minor code cleanup was done.

TkPasMan is a simple program that stores usernames and passwords for access to various websites.
It is inspired by gpasman, but has more `paste possibilities. For example, you can just paste username and then password behind it.
How To Use TkPasMan:
A. Entering a new site.
1. Choose `Add site from the Edit menu to add a new site you want to store your password for.
2. Type a clear description, and press .
3. Now you can type your username and/or password in the fields on the right.
4. Use the checkbuttons to adjust the way username and/or password will be copied into the primary X selection when you select a description. Most times, you will want to select the first two options, i.e. `Username and `Password.
B. Selecting username and password and pasting them elsewhere.
1. Point your mouse to one of the descriptions in the list on the left.
2. Just press your left mouse button, and, depending on your configuration of the checkbuttons, TkPasMan will select a username or password for you.
3. Now, point your mouse to the application you want to paste your username in.
4. Just press the middle mouse, and voil? the item will be pasted! TkPasMan will automagically put the next item (most times a password) in the X selection, so, after you pasted a username somewhere, just go to the place you want to paste the password, and again middle-click to put the password on its place.
Enhancements:
- Fixed the install procedure to use install instead of cp.

abrowse is a program which allows you to read AKAI S1000/3000 sample CDs and write the samples into wav audio format. It is written in perl.

mod_activex_filter is an Apache module that enables ActiveX filtering for Apache proxy.

This module is a small example of an Output Filter developed for Apache 2.0.44 and tested up to 2.0.46.

Its only a simple hack of mod_case_filter to get a way to filter ActiveX on a proxy. Actualy, the only way to filter ActiveX if your proxy is unable to do it is to use a TIS module chained with your proxy.

But the TIS is only capable of doing HTTP/1.0. If you need real performances, youll want to use HTTP/1.1.

Thats why I wrote this small module...

It has been generated with classical commands: apxs -g -n activex_filter and apxs -c -n

You just have to do make and make install to use it.

Dont forget to modify your httpd.conf.

Simple example of a working httpd.conf:

KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15

StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0

Listen 80

LoadModule activex_filter_module modules/mod_activex_filter.so
AddOutputFilter ActiveXFilter html
ActiveXFilter On

ProxyRequests On
User nobody
ServerAdmin brice@free.fr
ServerName trillian
UseCanonicalName Off
DefaultType text/plain
HostnameLookups Off
ErrorLog logs/error_log
LogLevel warn
ServerTokens Prod
ServerSignature On

GNUdap is a project to build a userspace driver to interface Linux with proprietary-protocol USB MP3 players and mass storage devices. Currently GNUdap supports the CHIC MP10, CHIC MP30, CHIC Symphony from "Perstel,Inc." and the NGS Jogger from the NGS Technology.
GNUdap is also an experiment to test the advantages of a strongly-typed programming language and of the functional programming paradigm in hardware developing. In fact GNUdap is developed using the Objective Caml programming language.
To access the devices, we use camlusb, an ocaml binding to libusb, wich is an library which works in userspace to access usb devices.
A shell, which supports the main features of the player, is provided. Besides being done for linux, unlike the original program provided with the MP10, this software is interesting because it has additional features (like being able to transfer mp3s directly to the pc, and to change the playable status of a file on the DAP), not present in the official one. A graphical frontend and a filesystem interface are planned.
To find more informations about the protocol, the driver and the shell visit the Documentation Page
Enhancements:
- chic.sh: Corrected the DIR variable
- added documentation