Free sunos software for linux

sh2log is a PTY sniffing program that captures all keystrokes and console output of physical and virtual consoles. sh2log works in userland and does not require the installation of a kernel module.

Consequently, it can be run on a wide range of different UNIX platforms. It provides ready-to-use log files and is meant to be used for legitimate purposes such as auditing user actions on a sensitive server or a honeypot.

How to install it

2.1. Edit config.h and setup the following values:

CONNECT_IP IP address of the machine on which sh2logd runs
SERVER_PORT UDP port in use by sh2logd
REAL_SHELL_DIR Directory for the real shells (/bin/shells)
MAX_LOG_SIZE Maximum size before a new log file is created
secret This is a 128-bit symmetric key used to secure
the data when transmitted over the network.

2.2. Compile sh2log by simply running "make system"

System can be any of those: linux, freebsd, openbsd, cygwin, sunos, aix, irix, hpux and osf.

2.3. Replace the original shell with sh2log and run sh2logd:

# mkdir /bin/shells/
# cp -p /bin/{sh,bash} /bin/shells/
# rm -f /bin/{sh,bash}
# cp -p sh2log /bin/bash
# cp -p sh2log /bin/sh
# ./sh2logd

If you see an error message about "bash: text file busy", check that you have rmed the file before copying sh2log over it. Also, Id recommended not running sh2log and sh2logd on the same machine.

Warning: /bin/sh is often a symlink to /bin/bash. DO NOT FORGET TO CREATE "/bin/shells/sh" OR YOUR SYSTEM WILL BE UNUSABLE!

3. Monitoring your users: the interactive log parser

Please try first to run ./parser with the provided sh2log example file "test.bin". Window resizing requires XTerm (not rxvt, eterm or konsole) and a valid DISPLAY; or if you use PuTTY, try resizing the window by hand.

The parser provides both non-interactive and interactive (takedown-like) modes of operation. In interactive mode, you can pause, fast forward (2x or 4x) and also follow in real time what the users are doing one the system, and have a live view of all terminals.

The OpenBSD project produces a FREE, multi-platform 4.4BSD-based UNIX-like operating system. Our efforts emphasize portability, standardization, correctness, proactive security and integrated cryptography.

OpenBSD project supports binary emulation of most programs from SVR4 (Solaris), FreeBSD, Linux, BSD/OS, SunOS and HP-UX. OpenBSD is freely available from our FTP sites, and also available in an inexpensive 3-CD set.

skill sends signals to processes given any combination of user names, ttys, commands, and pids and snice changes the priority of processes (given the same).
They are similar to kill(1) and renice(8), but the commandline is order-independent. There are also verbose, search, and interactive modes of operation.
Both programs run under a variety of operating systems, including:
Apple Darwin 5.4
AT&T SysVR4, SysVR4.2, SysVR4.2MP
4.2BSD, 4.3BSD, 4.4BSD (and many PC variants)
Cygwin 1.5 (uses Linux)
Mach 2.6, 3.0
DEC Ultrix 2.2, 4.1-2
DEC AXP OSF/1
DEC/Compaq Tru64 Unix V3.2D-2, T3.2F-1, V4.0, V5.0-1B
Encore UMAX 4.2
FreeBSD 2.0-2, 3.1, 4.4-11, 5.0-3, 6.0-1
HP-UX 6.5, 7.0, 8.0, 9.0-5, 10.1-20, 11.0-23
IBM AIX 3.1-2, 4.1, 5.2
IBM AOS 4.3
Linux 1.0-2, 2.1, 2.2, 2.4
MIPS UMIPS 2.1
NeXT OS 1.0, 2.1
NetBSD 1.3-5
OpenBSD 2.6, 3.0
Pyramid OSx 4.0
SCO UnixWare 7.0.1
SGI Irix 3.3, 4.0, 5.2, 5.3, 6.2, 6.5
Sequent Dynix 3.0-1
SunOS 2, 3, 4.0-1, 5.1-10
Enhancements:
- skill and snice now act on each process only once (for systems like BSD that return the same Process ID multiple times, once for each instantiated thread).
- Support has also been added for FreeBSD 6.2 and HP-UX 11.31.

SINGULAR is a computer algebra system for polynomial computations in commutative algebra, algebraic geometry, and singularity theory.
Its main computational objects are ideals and modules over a large variety of baserings. The baserings are polynomial rings over a field (eg. finite fields, the rationals, floats, algebraic extensions, transcendental extensions), or localizations thereof, or quotient rings with respect to an ideal.
It features fast and general implementations for computing Groebner and standard bases, including Buchbergers algorithm and Moras Tangent Cone algorithm. Its interactive shell and C-like programming language can be extended by libraries written in the SINGULAR programming language.
Main features:
- Main computational objects: ideals/modules over very general polynomial rings over various ground fields.
- Large variety of algorithms implemented in kernel (written in C/C++).
- Many more algorithms implemented as SINGULAR libraries.
- Intuitive, C-like programming language.
- Extensive documentation: Manual (info, ps, and html), Publications.
- Available for most hard- and software platforms: Unix (HP-UX, SunOS, Solaris, Linux, AIX), Windows, Macintosh.
Enhancements:
- This version is mainly a bugfix release, but it also contains some new features.
- Speed was improved for 64-bit architectures.
- The dmod.lib and perron.lib libraries were added.
- center.lib was improved. ncalg.lib was revised.
- New algorithms were added in primdec.lib.
- An improved version of slimgb was incorporated into groebner.
- The module generator (modgen) was improved.
- The build process was improved to build automatically without patches on 64-bit architectures.

Plan 9 From User Space is a port of the bulk of the Plan 9 software build environment to Unix.
While the libraries make an attempt to play nice with the rest of the system (by using the Unix rules for printf verbs and Unix system headers, for example), this port tries to reproduce the Plan 9 build environment as faithfully as possible, providing u.h and libc.h, and blithely redefining tokens such as open, dup, and accept in order to provide implementations that better mimic the Plan 9 semantics.
The result is a more complicated and less Unix-friendly environment, but Plan 9 programs can typically be compiled with little or no changes.
Most obviously, plan9port derives from Plan 9 from Bell Labs and would not exist without the work of the Plan 9 team over the past many years.
Rob Pike suggested the original X11 port of libdraw years ago, as part of drawterm, and strongly encouraged the Mac OS X work. He has also been a consistent source of good ideas to hide the ugliness of modern Unix.
William Josephson handled troff(1) (with Taj Khattra) and many of the supporting programs. He also inspired the thread library clean-up and has ported a handful of applications.
Andrey Mirtchovski and Axel Belinfante have done significant work dealing with X11 corner cases and fine-tuning rio(1). Axel never tires of finding bugs in the SunOS port.
Latchesar Ionkov has contributed many fixes to tricky bugs, and got factotum(4) up and running.
Many other people have provided help, ported programs, written bug reports, sent useful patches, and gotten plan9port running on new systems.
Bigelow & Holmes, Inc. created the screen fonts in the luc, lucm, lucsans, and pelm directories and granted permission to redistribute them with plan9port.
Enhancements:
- A FUSE-related bug was fixed. See http://lists.cse.psu.edu/archives/9fans/2006-July/048531.html

Linux VacationLinux vacation is a automatic mail-answering program. This is my vacation port to Linux. It is derived from the vacation program found on agate.berkeley.edu in the 386bsd directory on Nov 16, 1993. The original program was written by Eric Allman in 1983 and is copyrighted by the Regents of the UCB. The copyright disclaimer is valid for this distribution as well, i.e. this version is provided `as is, and I shall not be liable for any damage, data loss or earthquakes in the bay area.

Version 1.1 was a security-patched version. The former version 1.0 had a bad security bug which Olaf Kirch reported to the CERT mailing list (after giving me a hint :-). Please DO NOT LONGER USE vacation-1.0!

As far as Copyrights are concerned, the original parts of vacation are under the BSD copyright whereas I place my changed under the GPL (see file COPYING in the directory).

I tried to make this port look just like the version found with SunOS 4.1.x. There are minor differences, it resembles more the Sun version than the original 386bsd source.

Unpack the package as follows

mkdir -p /usr/src # if not already present :-)
chdir /usr/src
gzip -dc /vacation-1.1.tgz | tar xpvf -

A simple `make install (install-aout is no longer supported as of version 1.2) should install binary in /usr/bin and the manpages in /usr/man/man*, respectively. If you choose different directories, edit the Makefile.

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.