Free quotes software for linux

This program is a port of the famous BSD game fortune.
This program currently can only be run via the command line. It is ideal for use with various e-mail clients like pine,mutt etc. to insert random quotes at the end of your e-mail or for displaying a random quote when a user logs into your unix box. A more advanced application could be to display random tips in your program.
Main features:
- Written in Java, hence Platform Independent
- Handles multiple quote files.
- Supports fortune style cookie files.
- Supports passing various command line options. More options are being integrated in.
- Easily integrable into other JAVA programms.
- Easy and straighforward code.
- Licensed under GPL which means you can access the source code and make it better according to your likes.

Kuote is an applet for the KDE panel, inspired by Gnomes Wanda the Fish. It displays an animated character (a fish by default), which pops up quotes generated by the fortune(6) program when clicked (and optionally shows them in tooltips, too).
Kuote supports kioslaves for both the animation file and fortune files (fortune directories still work from local filesystems only). This means that you can enter any URL, not only local file names.
Try for example this fortune file available over WWW: http://hektor.umcs.lublin.pl/~mikosmul/computing/inet-fortune
It contains only two quotes, so for testing purposes use it as the only fortune file or assign it a high probability if you want to actually see these fortunes.
Main features:
- support for user-defined animations (file format compatible with Wanda the Fish)
- run fortune or any other program to generate quotes
- fortune can be configured through the GUI
Enhancements:
- added new animation: "See, Hear, Speak" (CC-BY-NC-SA license) - thanks to Mark Riedesel [Klowner]
- added French translation (thanks to Nicolas Ternisien)
- added "Next" button to fortune dialog
- fixed a memory leak associated with dialog boxes

XML Cleaner is a command line utility to filter and validate XML files.
XML Cleaner is written in Ada 9X and so it rather fast.
XML Cleaner is an XML filter and validator, similar to xmllint. It can remove superfluos namespace declarations from an XML file, expand XML entities, recode XML files, and more.
Main features:
- removes superfluous namespace declarations;
- Unicode support;
- (More to implement: XML validation, XML canonicalization, reformatting, whitespace removal, comments removal, XML charset recoding, XInclude processing, inplace file modification, etc.; XML Cleaner is to grow into a full featured command line XML filter and validator.)
XML Cleaner is developed to become xmllint replacement.
Enhancements:
- An option to choose whether or not to escape apostrophes and quotes in output was added.

Open Source Quotes DataBase is a Web site which is very similar in style to the bash.org QDB. Open Source Quotes DataBase is designed for people who would like to run their own quote sites.
Enhancements:
- The ability has been added for all admin users to change their own passwords, including mods.
- An error on some systems that stopped you from changing the admin password has been fixed.
- The voting page bug has been fixed.
- This will need a complete rewrite at a later stage.
- The browse function has been rewritten so that there are fewer problems with the page number output.
- The "Hacking Attempt" code has been fixed.

NoFuss Sales Tracker is a quote generation and tracking system designed for the general IT retailer.

NoFuss Sales Tracker project can create quotes from an internal price list using drop-down menus and pre-setup machine recipes.

The end product will keep information regarding clients in a database, be able to generate quotes on the fly, generate invoices from quotes, etc.

NoFuss Solutions provides expert IT services to the local community using experience in a variety of computer systems. We support both hardware and software and strive to provide a one-stop service to our customers. Our main target is the home user or small business owner that can not afford dedicated IT personnel but needs the services of a dedicated IT support office.

Apart from the general IT support services (repairs and maintenance) we also offer custom software development utilising the JAVA programming language. NoFuss Invoicing is a free invoicing solution for small businesses and we are currently working on a free point-of-sale application for the same market.

NoFuss Solutions came into existence during 1996 as Horn Labs and along with a shift in focus the beginning of 2005 the name changed to symbolise the new vision and direction of the business. The main aim of NoFuss Solutions shifted from providing services to corporate companies to providing the same services to smaller businesses, especially start-up companies. After restructuring the cost-structure we managed to focus on this relative low-income market and build a stable business on a very unstable market.

At the head of NoFuss Solutions is Ewald Horn, sole proprietor since 1996. Instead of trying to do everything in-house we have identified areas where we can out-source certain functions in order to provide a higher level of service to our customers. This enables us to focus on our strengths while still providing an all-round service to our customers.

Kwotes is a chat quote database system with a twist.

The quotes are publicly moderated, so its up to you to maintain the quality. All quotes are accepted and if their ranking falls too low for too long, they are deleted.

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.

Top level aggregator that will select a default lineup of site instances default lineup of site instancesof site instancesof site instancesof site instances from which to retrieve quotes.
Other than the default lineup, this module behaves identically to whichever site-specific module is first in the lineup. See below for site-specific modules.
METHODS
The basic user interface consists of several methods, as seen in the example above. Those methods are:
quotes()
Returns a list of rows (or a reference to an array containing those rows, if in scalar context). Each row contains the Symbol, Date, Open, High, Low, Close, and Volume for that date. Optionally, if non-adjusted values were requested, their will be an extra element at the end of the row for the Adjusted closing price.
dividends()
Returns a list of rows (or a reference to an array containing those rows, if in scalar context). Each row contains the Date and amount of the Dividend, in that order.
splits()
Returns a list of rows (or a reference to an array containing those rows, if in scalar context). Each row contains the Date, Post split shares, and Pre split shares, in that order.
source($ticker, $target)
Each of these methods displays which site-specific class actually retrieved the information, if any, for a particular ticker symbol and target such as quote (default), dividend, or split.
Enhancements:
- The internal structure was changed to use date iterators where appropriate.
- The documentation was fixed for MSN.
- Various minor edge cases were fixed.