Free pain software for linux

AFT is a document preparation system. It is mostly free form meaning that there is little intrusive markup. AFT source documents look a lot like plain old ASCII text.
AFT has a few rules for structuring your document and these rules have more to do with formatting your text rather than embedding commands.
Right now, AFT produces pretty good HTML, LaTeX, lout and RTF. It can, in fact, be coerced into producing all types of output (e.g. roll-your-own XML). All that needs to be done is to edit a rule file. You can even customize your own HTML rule files for specialized output.
Installation
- Run ./configure and then make install.
Enhancements:
aft-html.dat and aft-tex.dat
- Removed the historical hack: using to produce a line break. This was never documented, so it shouldnt cause too much pain to have it removed. If it does cause pain, let me know. You could always use a pragma to (re)implement this feature/hack.
- In the meantime... A new rule element: LineBreak has been introduced so that internal reliance on goes away. LineBreak has not been exposed to the end user (yet).
AFT.pm
- Fixed a small bug concerning line continuations in verbatim mode: Line continuations are no longer parsed when in verbatim mode. What you type is what you should get.

Menoku is an innovative new menu system that combines the best features of several common application launching schemes.
Menoku project lets you graphicaly search through neatly organized icons and choose any icon quickly with a short sequence of keys.
It supports hierarchical submenus and is easy to configure and organize with drag and drop interface. It works on Windows and Linux with the Qt4 library.
You have nine groups of nine icons, each of which can either launch an application or load a new menu of up to 81 icons.
Because of Menokus unique layout, any icon on the screen can be selected with at most two keypresses, expressing the position of the program you want to launch. You can memorize these key sequences, or hunt through a large full-color icons to find the program you want.
The idea behind Menoku is to make an application menu laid out like a Sudoku board. A single window is divided into nine groups of nine icons, making an array of nine by nine. Each icon can either load a new menu of up to 81 icons or can launch an application. To select an icon, you can either click on it or use your numberpad to select which group of nine icons to choose from and then which of the nine icons to activate. (See the Screenshots page if this isnt clear)
Why is this a good idea? Well, the purpose of Menoku is to try to make a more effecient menu system, and it does so by combining the best elements from several common application launching methods:
The Messy Desktop
Using the desktop to start applications is nice because it lets you browse through a large number of applications graphically using large icons. Unfortunately, keeping a desktop full of icons organized is a pain! Also, having launch icons on the desktop is really pretty inconvenient because you have to minimize windows to see all your icons. You shouldnt have to disrupt what youre doing to start a new program.
Menoku lets you graphically search through a large number of icons, just like a desktop, but its unique grouping layout enforces some level of organization, so you always know where to look. Also, Menoku is not a desktop, its more like a popup menu. It comes onto the screen when you ask for it (on top of any other windows) and when you select an application to start, it disappears.
Keyboard Shortcuts Sequences
Many power users like to use the keyboard to start their favorite programs. This means they dont have to move their hands to the mouse to start a new program, and its also much faster to just type out a memorized combination than to browse through a menu. Of course, the problem with this is that you have to memorize all your key combinations! You can make yourself a cheat sheet, but having to lookup a key combo before you type it defeats the purpose.
In Menoku, any icon you see on the screen is uniquely accessible through typing at most two keys: one to select which group of nine you want, and another to select one of those nine icons. This means that every application you want to start with Menoku has its own short key sequence. You can quickly memorize the sequences for your favorite programs, but if you forget you always have the icon display to remind you.
Hierarchical Menus
The standard way to start programs in a WIMP interface (such as Windows or X11) is to open up a menu. You click a button and get a long list of names and small icons, some of which represent programs and others more menus. The reason menus are so ubiquitous is that they work! You can store any number of programs that way and organize them into groups. Unfortunately, menus are very slow. You have to browse through text, which is inefficient, and you also have to wait for new menus to pop up beneath your mouse.
Menoku is in large part modeled after a standard hierarchical menu. Although you can only have 81 icons in any given menu, you can have any number of submenus which can also have 81 icons. You can easily group your programs together either by putting them into the same group of nine or by putting them in the same submenu. However, browsing in Menoku is much faster. You can search for large icons instead of text, and you can use your keyboard instead of following a winding path with your mouse.
Main features:
- Quick key-sequence launching of your favorite programs
- Mouse addicts can click on an icon instead of using the keyboard
- Trigger any command with any number of arguments
- Full color icons with transparency
- Tray icon for more menu-like functionality
- Configurable global hotkey
- Hierarchical menus in XML
- Drag and Drop menu editing
Installation:
First of all, to compile this code you MUST HAVE Qt 4.0 or above installed on your computer and you must use the version of qmake that comes with it.
To make sure you are using the right version of qmake, run the command "qmake -v" to see which Qt version it came with. Because the Qt libraries are in a state of transition from qt3 to qt4, you might have separate programs named qmake-qt3 and qmake-qt4, or something similar on your computer. If this is the case, use qmake-qt4 instead of qmake in the instructions below.
To compile Menoku, simply run:
qmake
make
If you use the wrong version of qmake, you will get error messages and the code will not compile.
The next step is to install. This will copy the menoku binary and the menoku icons into appropriate locations on your computer. The default place to put the binary file is /usr/bin/ and the default place for icons is /usr/share/pixmaps/. If you want to change these paths, edit the lines in menoku.pro that set target.path and icons.path so that they refer to the directories you want.
To install, make sure you have permissions for the intall directory (su root, if needed) and run:
make install
Enhancements:
Some minor bugfixes have been made.
Fixed the following:
- If you dragged a cell to another location then chose swap from the popup menu, youd get a segfault
- In some cases, changes in the number of icons would go unnoticed after drops (causing things like hiding empty cells and zooming single items to misbehave)

stephanie is a program for hardening OpenBSD for multiuser environments.

Mmmmm, OpenBSD. Functional, secure, free. With an emphasis on security and integrated cryptography, it carries an excellent reputation for plain old "you-just-cant-hack-this-ness". Not perfect, but nothing is, at least theyre not wearing suits and lying to you.

There are a few roles where i believe OpenBSD fits perfectly. One of these is in multiuser environments, where you have large numbers of possibly malicious users with local access. Here the OpenBSD teams commitment to auditing and fixing code provides a level trust in the environment which is hard to find elsewhere. Also, their efforts to provide integrated cryptography means setting up secure access is easy. So, lets take advantage of the freely available source and tailor it to our specific needs.

Details:

In Phrack 54, route|Mike Schiffman wrote a series of patches for OpenBSD 2.4 for Trusted Path Execution (TPE). Stephanie brings a modified version of these up to speed for OpenBSD 2.8 - 3.0, along with some additional features. A trusted path is one where the parent directory is owned by root and is neither group or other writeable. The TPE works off an internal list of trusted user ids. If a given user tries to execute a file not in a trusted path, and their user id is not in the kernels trusted list, they are denied execution privileges. In real terms, this means they cant download, compile and run krad-sploit.c.

In addition to the TPE, a series of privacy patches came along too. Originally supplied as patches for the individual utilities, these are now implemented through kvm(3), and honour trusted users (ie, trusted users are allowed to see all system information). As a practical example, this means that untrusted users will only be able to see information about processes they own, and the stat tools (netstat, iostat, vmstat, etc) will generally be broken for them. It has been pointed out that by going through trying to kill every possible process id you can find other users processes, but you cant really gain any information on them, so this is not really a great concern.

The original TPE patches had one known way of bypassing the execution restrictions, which was using shell redirection to allow arbitrary interpreted language scripts to be run (perl, sh, etc). This has been fixed up, but could possibly be a big pain in the ass, so please pay attention. When an interpreter is invoked, like most things, it creates a new process group with a job count of one. When a series of commands are connected via the | character on the command line, all the commands belong to the same process group and the job count represents the number of commands eg ps -ax | grep something | awk {print $1} has a job count of three, and the ps, grep and awk processes all belong to the same process group.

The one exception to this is when a user logs in, where we find their shell has its job count set to zero. So how can we use this to prevent shell redirection for a given set of programs? We need to be able to distinguish between ordinary commands and interpreters. At the moment this is done by setting the immutable flag on them. So, in kern_exec(), if we find an untrusted user executing something with the immutable flag set and a job count greater than zero, we flag the process as being potentially dodgy. Then in other system calls we disallow read()ing from fd 0 (stdin) and things like dup2(0, n) if the process has been flagged.

There are two main disadvantages to this. First is the system will need to be brought down to single user mode if the interpreter needs to be patched, and secondly, people will have a hard time suing to an untrusted user. Of course, when a user has shell, they can still type any commands that could otherwise be placed in a shell script, but at the least, this will raise the bar a bit.

Finally, Stephanie brings restricted symbolic links, ala the openwall patches for linux. As time permits, im still working on adding additional features, and will add bits of the openwall stuff i like. The basic goal is to add an extra layer of security without being a monumental pain in the ass to legitimate users, so some things wont be there. I havent added the additional hard link restrictions of the openwall patch, but will do something about this later as time permits.

Installing:

Step by step instructions are presented in the install guide which comes with the source. Read it all first, but its reasonably straight forward. It would be a good idea to read the original article (local copy) if you havent already.

Its distributed under the original two clause BSD license, mess with it all you want, but dont get cranky at me if it breaks something.

You can also read the tpe_adm(8) man page online.

DGNLib is a small C/C++ library for reading and writing DGN files.
Building:
This is a preliminary source distribution, and I have not gone to any pains to make it easy to configure and build. To build please do the following:
1. Update cpl_config.h to represent your platform accurately. Generally all that matters is to #define WORDS_BIGENDIAN on big endian platforms. The rest can likely be ignored.

2. Compile the sample program. On unix this can be accomplished something like:
% gcc dgndump.c *.cpp -lm -o dgndump
Enhancements:
- This release adds support for Bsplines, shared cell definitions, and text nodes.
- 3d solids and surfaces have been fixed.

GIMP circle brushes provides circle brushes for use as "rubber stamps" in the GIMP.

GIMP circle brushes can be used with one click instead of creating outline circles by making a circle, filling with black, shrinking, and filling with white.

The following pixel sizes are provided: 6, 12, 15, 20, 24, 30, 40, 50, 60, 80, 100, 140, 200, 300, 400, 500, and 600.

Circle brushes are my third brush collection for use in the GIMP.

It was brush week for me.

Making circles is a bit of a pain with the GIMP. I know the Make a circular selection,
fill it black, shrink it, fill it white thingy -- but come on already... if I can rubber stamp a
premade circle brush where I need it instead, wouldnt that be kinda nice?

These were fairly easy, in theory. I had to add a bit of extra feathering to the above technique to get nice circles in all the sizes. Also several 45-degree rotations which smoothed out a lot of upper-end noise.

I also tried exporing from Inkscape, but the paths I converted to bitmaps did not work out as well as I had hoped and wound up sticking with the GIMP to create all
of them.

Sizes I made are:

6,12,15,20,24,30,40,50,60,80,100,140,200,300,400,500 and 600.

Use them for anything youd like. If you redistribute them, please include this file.

I post these, and perhaps make updates, at gimphelp.org. All the items will also be included (in png format) at wpclipart.com, the Public Domain clipart site.

Installation:

Stick them in the GIMP brushes folder and either "refresh brushes" or restart the GIMP. I put them in the system-wide folder, on my Slackware machine this folder is located at: /usr/share/gimp/2.0/brushes

You should also have a local brushes folder at: ~/.gimp-2.x/brushes

Luban is a component oriented scripting language. Luban is free and open source. Luban is named after a legendary ancient Chinese civil engineer and carpenter two thousand year ago whose constructions are still in use today.
The programming language spectrum seems crowded. Do we have all the tools we need? The author of Luban likes the scripting languages in general because of their usability. Though he always feels the pain for the lack of suitable component model for scripting.
And he personally considers object oriented scripting is too complicated for scripting purpose and will never compete with C++/Java. He eventually created Luban, a scripting language with a robust component model tailored for scripting purpose. Luban is an easy scripting language that is as clean and manageable as Java.
There have been numerous discussions about software component without clear definition. Lubans definition of component is property based object that is similar to Java Bean. User interacts with component by reading and writing property values, and computation could be triggered by the interactions.
The idea of Luban programming language that scripting language needs a different component model other than conventional class hierarchy to fit its scripting environment. A complete mechanism is built in Luban to define, save and categorize components, which is a fundamental feature of Luban.
Enhancements:
- This release adds the new feature to iterate through the elements in Java container objects.
- The following Java types can now be iterated in Luban: Java array, java.util.Collection, and java.util.Map.

HTML::EP is a system for embedding Perl into HTML.
SYNOPSIS
< html >< head >< title >CGI-Env< /title >< /head >
< ep-comment >
This is an HTML document. You see. Perhaps you wonder about
the unknown HTML tags like ep-comment above? They are part
of the EP system. For example, this comment section will
be removed and you wont see it in your browser.
< /ep-comment >
< ep-perl >
# This is an example of embedding Perl into the page.
# We create a variable called time, containing the current
# time. This variable will be used below.
my $self = $_;
$self->{time} = localtime(time());
; # Return an empty string; result becomes embedded into the
# HTML page
< /ep-perl >
< body >< h1 >The current time< /h1 >
Your HTML::EP system is up and running: The current time is $time$.
< /body >
< /html >
NEWS
HTML::EP does now have a homepage, a CVS repository and a bug tracking system. Try
http://html-ep.sourceforge.net/
Have you ever written a CGI binary? Easy thing, isnt it? Was just fun!
Have you written two CGI binaries? Even easier, but not so much fun.
How about the third, fourth or fifth tool? Sometimes you notice that you are always doing the same:
- Reading and parsing variables
- Formatting output, in particular building tables
- Sending mail out from the page
- Building a database connection, passing CGI input to the database and vice versa
- Talking to HTML designers about realizing their wishes
You see, its soon to become a pain. Of course there are little helpers around, for example the CGI module, the mod_perl suite and lots of it more. Using them make live a lot easier, but not so much as you like. CGI(3). mod_perl(3).
On the other hand, there are tools like PHP or WebHTML. Incredibly easy to use, but not as powerfull as Perl. Why not get the best from both worlds? This is what EP wants to give you, similar to ePerl or HTML::EmbPerl. I personally believe that EP is simpler and better extendible than the latter two. ePerl(1). HTML::EmbPerl(3).
In short, its a single, but extensible program, that scans an HTML document for certain special HTML tags. These tags are replaced by appropriate output generated by the EP. What remains is passed to the browser. Its just like writing HTML for an enhanced browser!