Free sunos software for linux

thttpd is a simple, small, portable, fast, and secure HTTP server:
Simple; It handles only the minimum necessary to implement HTTP/1.1. Well, maybe a little more than the minimum.
Small; See the comparison chart. It also has a very small run-time size, since it does not fork and is very careful about memory allocation.
Portable; It compiles cleanly on most any Unix-like OS, specifically including FreeBSD, SunOS 4, Solaris 2, BSD/OS, Linux, OSF.
Fast; In typical use its about as fast as the best full-featured servers (Apache, NCSA, Netscape). Under extreme load its much faster.
Secure; It goes to great lengths to protect the web server machine against attacks and breakins from other sites.
It also has one extremely useful feature (URL-traffic-based throttling) that no other server currently has. Plus, it supports IPv6 out of the box, no patching required.
Enhancements:
- Move fdwatch initialization before the chroot, so that /dev/poll can work.
- Multiple fdwatch cleanups and fixes (Adam Zell).

Anti-Web project is a single-process, light-weight, non-threaded webserver that emphasizes simplicity, efficiency, and security.
AW 3 is the result of a rewrite of the webservers internals and represents much thought, effort, and careful design by the AW team.
With a few (perhaps signifigant) exceptions, AW 3 should be drop in compatible with AW 2. To use this drop in compatibility, refer to the "Simple Configuration" section. If you want to use some of AW 3s more advanced features, refer to the "Complex Configuration" section.
Your rights to use, distribute, and modify AW are protected by the GNU GPL license. Please see the file COPYING for more details.
Compilation
You should be able to compile AW simply by extracting it, changing into the extracted directory and typing
make
If all goes well, you should end up with an executable called "awhttpd".
If all does not go well, check the top of the file Makefile for compilation options. You will need to do this for a SunOS compilation, for instance.
Enhancements:
- Some extra CGI functionality was added.

NRIA is New Region of Interest Analysis.

NRIA is a medical image processing program developed at the Brain Behavior Laboratory (BBL) of the University of Pennsylvania; it specializes in the quantitative analysis of PET and MRI images of the brain. The perpetrators are listed in the Credits file.

Despite a nearly total lack of user documentation, NRIA is used heavily at BBL and has been carried by ex-students to infect a few other universities. The only known way to learn how to use the program (unless you wrote it yourself) is to get hands-on training by someone else who already knows how to use it.

NRIA currently runs under Solaris (aka SunOS 5 or greater). A port to any other platform is unlikely, due to the prevalence of non-portable constructs in the code. NRIA will compile but not run successfully using gcc on Linux/Intel; no one is known to have tried it on Linux/Sparc.

Bug reports may be sent to Paul Hughett (hughett@bbl.psycha.upenn.edu), who will add them to his collection. Bug fixes and other improvements may be sent to the same person; context diffs are the preferred format. Should you want to make a more substantial contribution, read the file CodingStyle.

If you still want to install NRIA, see the INSTALL file for instructions. The COPYING file describes the license terms under which the software is made available.

Installation:

These instructions assume that you will put the source tree (where the program is compiled) in a directory /usr/local/src/nria and the executable programs and shared data in a directory /usr/local/nria; if you place them elsewhere, make the appropriate modifications to these instructions.

1. Unpack the source tree with the commands

cd /usr/local/src
gunzip nria-1.0.6.src.tgz
tar xf nria-1.0.6.src.tar

2. Compile NRIA and its supporting programs with the commands

cd nria-1.0.6
make clean
make all

The compiled executables will be placed in one of the directories arch/Linux/bin, arch/SunOS-4/bin, or arch/SunOS-5/bin, depending on your machine architecture and operating system version. (Note that NRIA will compile but not run successfully on Linux; if you want to really use the program you will need a Sun.)

Compiling the whole thing takes about 20-30 minutes, so you might as well go get a cup of coffee while youre waiting. There are about a thousand or so compiler warnings that havent been fixed yet; ignore them.

3. Install the binaries and man pages by

cp -p arch/SunOS-5/bin/* /usr/local/nria
cp -p man/man1/*.1 /usr/local/man/man1

If this is a new installation, install the shared data by

cp -p nria/share/* /usr/local/nria

If this isnt a new installation, you will need to figure some way of merging the new shared data with any local modifications.

You will probably need to be root to do the installation; on the other hand, you can install them in your personal home directory without being root.

4. Add /usr/local/nria to your path, if not already there:

If you are using csh as your shell, then place the following at the end of your $HOME/.login file:

set path = ($path $NRIA)

If you are using sh, ksh, or bash as your shell, then place the following at the end of your $HOME/.profile file:

PATH=${PATH}:$NRIA
export PATH

5. To run NRIA, re-login or type the above appropriate path commands at your shell prompt, and then type:

nria

If you dont have any .nhdr files in the current directory, you will see an empty file dialog. You will need to change directories to one which holds nria format images (raw *.img file, header *.nhdr file). If you only have raw images, then for each image you will need to use the img2ria program (type "man img2ria" for more details). If you have individual slices in their own files, you will need to concatenate all slices into one raw image file, and then run img2ria. NRIA is designed to work with 3D multi-slice volumes, not individual 2D slices.

CDDB is a Perl module that can read the CDDB entry for an audio CD in your drive.

SYNOPSIS

use CDDB_get qw( get_cddb );

my %config;

# following variables just need to be declared if different from defaults

$config{CDDB_HOST}="freedb.freedb.org"; # set cddb host
$config{CDDB_PORT}=8880; # set cddb port
$config{CDDB_MODE}="cddb"; # set cddb mode: cddb or http
$config{CD_DEVICE}="/dev/cdrom"; # set cd device

# user interaction welcome?

$config{input}=1; # 1: ask user if more than one possibility
# 0: no user interaction

# get it on

my %cd=get_cddb(%config);

unless(defined $cd{title}) {
die "no cddb entry found";
}

# do somthing with the results

print "artist: $cd{artist}n";
print "title: $cd{title}n";
print "category: $cd{cat}n";
print "cddbid: $cd{id}n";
print "trackno: $cd{tno}n";

my $n=1;
foreach my $i ( @{$cd{track}} ) {
print "track $n: $in";
$n++;
}

This module/script gets the CDDB info for an audio cd. You need LINUX, SUNOS or *BSD, a cdrom drive and an active internet connection in order to do that.

Pimd-dense is a lightweight, stand-alone PIM-Dense Mode implementation that may be freely deployed or distributed. Pimd-Dense implements the full PIM-DM specifications but there are few exceptions noted in the Release Notes.
The code from Pimd-dense is heavily based on the PIM-Sparse Mode daemon implementation by Puneet Sharma and Charley Liu (USC), Ahmed Helmy (SGI/USC), and Pavlin Ivanov Radoslavov (USC). For more info on PimD-Sparse, see the PIM Home Page at USC
Use of PimD-Dense for multicast routing requires a separate facility for unicast routing such as (1) static routes via the UNIX route command, (2) RIP routes via the standard UNIX routed routing daemon, or (3) other dynamic unicast routing protocols such as those provided by the GateD multiprotocol routing daemon.
PimD-Dense is currently ALPHA-version software that yet requires extensive testing. If you choose to use it, information about any bugs or problems sent to kurtw@antc.uoregon.edu would be greatly appreciated and will be investigated ASAP.
PimD-Dense should compile and run on most UNIX varieties, including FreeBSD, BSDI, NetBSD, SunOS, IRIX, Solaris 2.5, Solaris 2.6, and Linux (however it has not yet been tested on all these).
Many current version of the IP MRouting kernel code requires patches to correct certain bugs in order to work correctly with PimD-Dense. Before using PimD-Dense, you should apply one of the current patches available for PimD-Sparse from USCs PIM FTP site.
Enhancements:
- Fixed entry timer initialization in route.c:process_cache_miss

BlackMail is a highly configurable SMTP mail filter that runs at a system level as a proxy to your existing mailer. Selectively reject bogus or spam mail during receipt, saving you extra storage space or irate users.
Blackmail operates at a system-wide level: all incoming and optionally outgoing mail is filtered.Will block unwanted mail relaying (if your mailer is unable to) and spams.
The filtering consists of various checks on the SMTP envelope and message headers: if any tests fail then the mail will be bounced. Blackmail can...
Check against spam sites
Check against spam keywords
Check host names and email addresses using DNS for validity
Check against the RBL (Realtime Blackhole List) for spam IP addresses
Check that To: and From: address do not match (a common spam signature)
Check correct header formation e.g. Message-ID
The spam sites and spam keywords are of your choice, you can block who or what you want. Minimal sample lists are provided.
BlackMail is known to work with:
Mailers: Smail, Sendmail, Qmail, Fetchmail
OSes: Aix, various BSD, Irix, Linux, NeXTStep 3.x, Solaris, SunOs, SVR4 (Re-confirmation is required for some of these OSes.)
It should be possible to use BlackMail with most SMTP mailers on most UNIX systems. Blackmail is not designed to run on Windows or OS/2, but if you wish to port it...
Enhancements:
- Removed old reference to www.bitgate.com

Ygl emulates SGIs GL routines under X11. It compiles fine under AIX >3.2, HP-UX >7.0, Linux with XFree/Xorg, SunOS, ConvexOS, Mac A/UX, Mac OS/X and many others, but needs an ANSI-C compiler (gcc is ok). The library was written for two reasons:
On our RS/6000 GT4 hardware, 2D Ygl is up to twenty times faster (circf()) than GL (strange, isnt it?...)
2D (and 3D using OpenGL) graphics runs on non GL hardware and even on remote X-Servers.
Included are most of the two-dimensional graphics routines, the queue device routines, the query routines, doublebuffering, RGB mode with dithering, window attribute routines, FORTRAN bindings and more (see below).
3D stuff was added with version 4.0 using OpenGL calls.
Since Version 2.8, all Ygl functions do have a FORTRAN interface. The FORTRAN versions of all functions have an underscore appended, so the FORTRAN compiler must append a _ to all function names. f2c does this, xlf (under AIX 3.2) requires the option -qextname. See smile_f77.f for an example program. Set FortranBindings to 0 in Imakefile or change Makefile.std if you dont want these bindings. FORTRAN bindings are not tested because I have no programs.f to test. If you find bugs, feel free to report them to me.
You can always find the latest version of Ygl in the directory ftp.thp.Uni-Duisburg.de/pub/source/X11/.
Note that perl, python and tcl bindings for Ygl are available here thanks to Prabhu Ramachandran.
Enhancements:
- Added gsync() (only works with OpenGL bindings).
- Added {XY}MAXSCREEN macro
- Removed poly*() from Ygl.h, as they are not implemented yet.