Free hacksaw jim duggan software for linux

Firewall by Jim is a firewall that takes advantage of tcp_wrappers information to block users. I got tired of the firewall scripts out there not doing what I wanted them to.. I wanted a firewall that was flexible to use, but did its job. I wanted one that could be configured to any circumstance easily without changing the script itself. That is why I designed my firewall to use simple text files for configuration ease.

I have built in mutlple mean of protection into the firewall itself. Of the most notable is the hacker, trojan, spam, and blacklist capabilities.

The hacker protection will prevent the outside world from running unwanted commands. If you choose to enable this function.

The hacker protection will prevent the outside world from running unwanted commands. The trojan protection has two different levels. Standard and Intensive. The standard protection only protections from known linux and unix trojans. Where as the intensive will protect from all known trojans from windows, linux, and unix based.

The spam protection will block any IP address which is in list, from sending mail to your SMTP server.

The blacklist protection will block total communications to a site. I have also included a blacklist update script which will pull blacklist information from http://www.dshield.org .

Software::Packager::Aix is the Software::Packager extension for AIX 4.1 and above.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(aix);

This module is used to create software packages in a Backup-format file (bff) suitable for installation with installp.

This module creates packages for AIX 4.1 and higher only. Due to the compatability requirements of Software::Packager multiple components in the same package are not supported. This may be changed at some point in the future.

This module is in part a baised on the workings of the lppbuild scripts. Where possible Ive worked from the standards, where I had no idea what they were talking about I refered to the lppbuild scripts for an understanding.

As such Id like to thank the writers of lppbuild version 2.1. I believe these scripts to be written by Jim Abbey. Who ever it was thanks for your work. It has proven envaluable. lppbuild is available from http://aixpdslib.seas.ucla.edu/

ParaView project is an application designed with the need to visualize large data sets in mind. The goals of the ParaView project include the following:
- Develop an open-source, multi-platform visualization application.
- Support distributed computation models to process large data sets.
- Create an open, flexible, and intuitive user interface.
- Develop an extensible architecture based on open standards.
ParaView runs on distributed and shared memory parallel as well as single processor systems and has been succesfully tested on Windows, Linux and various Unix workstations and clusters. Under the hood, ParaView uses the Visualization Toolkit as the data processing and rendering engine and has a user interface written using a unique blend of Tcl/Tk and C++. Please go here for a detailed list of features.
ParaView was created by Kitware in conjunction with Jim Ahrens of the Advanced Computing Laboratory at Los Alamos National Laboratory (LANL). Contributors and developers of ParaView currently include: Kitware, LANL, Sandia National Laboratories, and Army Research Laboratory. ParaView is funded by the US Department of Energy ASCI Views program as part of a three-year contract awarded to Kitware, Inc. by a consortium of three National Labs - Los Alamos, Sandia, and Livermore. The goal of the project is to develop scalable parallel processing tools with an emphasis on distributed memory implementations. The project includes parallel algorithms, infrastructure, I/O, support, and display devices. One significant feature of the contract is that all software developed is to be delivered open source. Hence ParaView is available as an open-source system.
Main features:
- Handles structured (uniform rectilinear, non-uniform rectilinear, and curvilinear grids), unstructured, polygonal and image data.
- All processing operations (filters) produce datasets. This allows the user to either further process or save as a data file the result of every operation. For example, the user can extract a cut surface, reduce the number of points on this surface by masking, and apply glyphs (for example, vector arrows) to the result.
- Contours and isosurfaces can be extracted from all data types using scalars or vector components. The results can be colored by any other variable or processed further. When possible, structured data contours/isosurfaces are extracted with fast and efficient algorithms which make use of the special data layout.
- Vectors fields can be inspected by applying glyphs (arrows, cones, lines, spheres, and various 2D glyphs) to the points in a dataset. The glyphs can be scaled by scalars, vector component or vector magnitude and can be oriented using a vector field.
- A sub-region of a dataset can be extracted by cutting or clipping with an arbitrary plane (all data types), specifying a threshold criteria to exclude cells (all data types) and/or specifying a VOI (volume of interest - structured data types only)
- Streamlines can be generated using constant step or adaptive integrators. The results can be displayed as points, lines, tubes, ribbons, etc., and can be processed by a multitude of filters.
- The points in a dataset can be warped (displaced) with scalars (given a user defined displacement vector) or with vectors (unavailable for non-linear rectilinear grids).
- With the array calculator, new variables can be computed using existing point or cell field arrays. A multitude of scalar and vector operations are supported.
- Data can be probed at a point or along a line. The results are displayed either graphically or as text and can be exported for further analysis.
- ParaView provides many other data sources and filters by default (edge extraction, surface extraction, reflection, decimation, extrusion, smoothing...) and any VTK filter can be added by providing a simple XML description (VTK provides hundreds of sources and filters, see VTK documentation for a complete list).
Enhancements:
- This release adds parallel uniform rectilinear grid volume rendering (vtkImageData).
- It introduces new algorithms for parallel unstructured grid volume rendering.
- Support for hardware accelerated offscreen rendering using OpenGL framebuffers.
- Improved multi-block support.
- Improved AMR support.
- Animation saving with ffmpeg.
- Filters have been added for FLUENT, OpenFOAM, MFIX, LSDyna, and AcuSolve.
- A gradient filter for unstructured data.
- Many other enhancements and bugfixes.

mod_auth_shadow is an Apache module for authentication using /etc/shadow.

When performing this task one encounters one fundamental difficulty: The /etc/shadow file is supposed to be read/writeable only by root. However, the webserver is supposed to run under a non-root user, such as "nobody".

mod_auth_shadow addresses this difficulty by opening a pipe to an suid root program, validate, which does the actual validation. When there is a failure, validate writes an error message to the system log, and waits three seconds before exiting.

Laptop-Hotswap kernel module enables hot-swapping for disk drives with full DMA support under Linux. It requires kernel 2.6.15+ and ACPI.
I think it ought to work on just about any laptop, although Im not as familiar with ACPI as Id like to be. It works fine on my T22. There could be issues with laptops with two expansion bays -- I shut down the entire ide1 interface and fire it back up, and I do all my watching on the ACPI device for the IDE1/Master. So if you had a slave device, and you ejected the master, your slave will go bye-bye. Thinking about ways around that, but they dont export too much of the ide driver. I think itd be easy to handle, you just have to make sure youre not using either master or slave whenever you eject one of them.
At least on my laptop, dont go pulling things while your laptop is sleeping. Do it when its awake.
The floppy support should work, but my floppy drive isnt with me right now.
Theres one parameter -- auto_eject. If you set it to 1, the driver will automatically shut down and unregister the IDE interface upon getting a request for ejection (On my T22, I pull a little switch and a lever pops out -- the drive is still connected at that point, but it shows as a request for ejection). If your laptop doesnt have a mechanism for that:
echo -n "MSTR eject" > /proc/acpi/lths
Will shut down and software-eject the drive, and you can safely pull it and insert another.
See the scripts in config/ -- theyre made to work with acpid to handle the ejection and umounting and insertion. The mount/umount stuff only matters for a drive caddy, I suppose.
It shouldnt matter what you have in your laptop at boot. This module also fixes that annoying thing on my T22 where if I dont have a ultrabay battery in at boot, I cant ever see its status.
Enhancements:
- Support for the Fujitsu S7020 (and possibly other laptops using a PATA bay with an SATA main disk).

Basset::Object::Persistent is a subclass of Basset::Object that allows objects to be easily stored into a relational database. Presently only supports MySQL, but that may change in the future.

SYNOPSIS

(no synopsis, this is an abstract super class that should never be instantiated directly, it should be subclassed for all persistent objects and used through them)

Basset::Object is the uber module in my Perl world. All objects should decend from Basset::Object. It handles defining attributes, error handling, construction, destruction, and generic initialization. It also talks to Basset::Object::Conf to allow conf file use.
But, some objects cannot simply be recreated constantly every time a script runs. Sometimes you need to store the data in an object between uses so that you can recreate an object in the same form the last time you left it. Storing user information, for instance.

Basset::Object::Persistent allows you to do that transparently and easily. Persistent objects need to define several pieces of additional information to allow them to commit to the database, including their table definitions. Once these items are defined, youll have access to the load and commit methods to allow you to load and store the objects in a database.

It is assumed that an object is stored in the database in a primary table. The primary table contains a set of columns named the same as object attributes. The attributes are stored in those columns.

Some::Package->add_attr(foo);
my $obj = Some::Package->new();
$obj->foo(bar);
$obj->commit();

in the database, the foo column will be set to bar.

Schedule::Oncall module contains methods for managing an on-call schedule.

Schedule::Oncall provides methods to manipulate an on-call schedule. One or more tables of schedules can be maintained, loaded, and searched. An on-call table is composed of seven days, where each day has a list of minute ranges which correspond to a particular person.

Information such as email address, pager number, etc. may be stored in the schedule configuration file. Simple variable assignments may also be made. Other textual information may be stored in the schedule in order to assist other applications (e.g., html headers or email body text), and variables substitution may occur within the text blocks.

Schedule files may be chosen based on weekly or monthly rotations, relative to the first week or month of the year. Weekly schedules begin on a Monday and end on a Sunday, the same as strftime(3)s %W" format. Each rotation is stored in a separate file, and the appropriate rotation is chosen at load time.