Free sparc mac1 software for linux

arp-scan sends ARP (Address Resolution Protocol) queries to the specified targets, and displays any responses that are received.
It allows any part of the outgoing ARP packets to be changed, allowing the behavior of targets to non-standard ARP packets to be examined. The IP address and hardware address of received packets are displayed, together with the vendor details.
These details are obtained from the IEEE OUI and IAB listings, plus a few manual entries. It includes arp-fingerprint, which allows a system to be fingerprinted based on how it responds to non-standard ARP packets.
Enhancements:
- Support for Sun Solaris was added.
- This was tested on Solaris 9 (SPARC).
- The following new arp-fingerprint patterns were added for ARP fingerprinting: IOS 11.2, 11.3, and 12.4; ScreenOS 5.1, 5.2, 5.3, and 5.4; Cisco VPN Concentrator 4.7; AIX 4.3 and 5.3; Nortel Contivity 6.00 and 6.05; Cisco PIX 5.1, 5.2, 5.3, 6.0, 6.1, 6.2, 6.3, and 7.0.
- IEEE OUI and IAB MAC/Vendor files were updated.
- HSRP MAC address was added to mac-vendor.txt.

LuBu OpenMagic is an enhancement of the Solaris OpenStep 1.1-sparc desktop enviroment.

It is not a rewrite, nor is it a re-release, but is a package that enhances and improves (and includes) Solaris OpenStep 1.1.

LuBu OpenMagic is only available for the SPARC architecture.

LuBu OpenMagic 1.0 is a heavily modified version of the Lighthouse OpenStep 1.1
release for the Sparc platform. It is not a theme, nor a reconfiguration, but
an almost pure rewrite of non-binary files (runtime configurations, application
definitions, enviroment variables, and many functions). In some parts entire functions
have been replaced features have been added. This applies primarily to the Wrapper
function which has been entirely rewritten to use the LuBu OpenMagic Alert System
(aka: LOAS). This is a completely new feature which among many other things also
produces error messages in human readable form, with the actual cause of the error.
This makes taking countermeasures and avoiding future errors easier. The default
application definitions provided with OpenStep 1.1 were the cause of countless bugs,
and I have spendt a great amount of time optimizing the default defs. There are still
a few bugs for which I have found no workaround, but non are critical.

OpenMagic 1.0 will only run on Sparc CPUs since it is based on Solaris OpenStep 1.1 for Sparc. There is not, nor will there ever be, a release for any other CPU. Since
LuBu OpenMagic 1.0 is based on the binary Solaris OpenStep release, it remains a
Solaris Sparc product. There are no known binaries for other CPUs or operating
systems. It does however fully integrate the Solaris Operating Enviroment, Common
Desktop Enviroment, and any other enviroments that run on Solaris Sparc. This makes it alot easier to integrate applications into the OpenStep enviroment without the need of porting.

LuBu OpenMagic 1.0 is packaged as a pure gzipped tar file, intended for unpacking
from the root directory (ie: / ). This means that the default installation directory for OpenStep should be /usr/openstep - it is importent that this rule is followed, else the installation will fail and the distribution will not function at all. It is however possible to extract to a different directory and create a symlink to /usr/openstep. Just remember to copy the etc/dt/config files to their desired location (/etc/dt/config). This is needed as there are some additional files included in order for LuBu OpenMagic 1.0 to function correctly:

1. A modified /etc/dt/config/Xservers file with -dpi 72
2. Configuration files for dtlogin (in /etc/dt/config/*.os|*.xpm)
3. Icons for /cdrom and /floppy (directories will be created if missing)

For an optimal installation:

$ su -
# cd /
# gtar zxvf /path/to/lubu_openwb-1.0-sparc.tgz

Make sure that all the files are extracted, and that existing files ARE overwritten! This will NOT reduce system security or in any other way reduce system performance.

Make sure all files in /usr/openstep are owned by bin:bin else you will loose alot of functionality! There is NO NEED for ANY of the files to be owned by root (other than possibly Preferences.app/set_password which is initially broken due to a missing library - see KNOWN_BUGS).

If you must chown /usr/openstep, then it is a good idea to cd to /usr before running chown -R in case you are using a non-standard chown. Worst case scenario is that a chown -R from / chowns your entire system bin:bin! Better safe than sorry.

# cd /usr
# chown -R bin:bin openstep/

If you extracted OpenStep to a different location, then cd to that location before running chown

# cd /path/to/your/installation
# chown -R bin:bin ../openstep (provided you actually are in the openstep directory)

Make sure the following line is present in /etc/dt/config/Xservers:
:0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner -dpi 72
(this is however included in the distribution files and should be installed upon
extraction). For optimal performance it is best to run your display at -depth 24 -dpi 72

This file (Xservers) should be -rwx-xr-x otherwise run
# chmod 755 /etc/dt/config/Xservers

It is vital that dtlogin is restarted after installation. Exit your windowmanager, login as root to the system console, and run the following commands (as root):

# sh /etc/init.d/dtlogin stop
# sh /etc/init.d/dtlogin start

Now log out from the console and allow the dtlogin loginwindow to reappear.
Select "LuBu OpenMagic 1.0" from the session menu. Log in and enjoy!

It is however possible to run LuBu OpenMagic 1.0 without CDE installed, or without running it through dtlogin by simply starting the file /usr/openstep/bin/openstep:

$ sh /usr/openstep/bin/openstep

though you might loose some valuable configurations using this method.
It has not as of yet been tested thouroughly.

AFS is a distributed filesystem product, pioneered at Carnegie Mellon University and supported and developed as a product by Transarc Corporation (now IBM Pittsburgh Labs).
It offers a client-server architecture for file sharing, providing location independence, scalability and transparent migration capabilities for data.
IBM branched the source of the AFS product, and made a copy of the source available for community development and maintenance. They called the release OpenAFS.
Enhancements:
- OpenAFS 1.4.0 adds large file support in Unix and Unix-like clients and in servers.
- Kerberos 5 integration has been improved. aklog now ships with OpenAFS 1.4.0.
- Several new operating system versions are now supported, including Solaris 10 on both SPARC and Intel.

SAStk is Slackware Administrators Security tool kit. We aim to provide a set of tools and utilities to install and maintain a reasonable level of security for the Slackware Linux distribution.

We added support for other security aspects such as password aging and similar configuration for the machine.

Install

Please see INSTALL for instructions on installing SAStk.

Build Environment for the application

We tested the scripts on x86 Slackware 8.0.

We could use a tester or two using Sparc and Alpha Slackware to make sure nothing breaks based on the architecture.

Splack Linux is Slackware for Sparc.

Splack supports all Sun4c, Sun4d, and Sun4m hardware.

Most Sun4U (Ultrasparc) machines are supported, but the more modern SunBlade and SunFire systems are not supported in the 2.2.20 kernel.

As a workaround you may be able to move the boot disk to a supported UltraSparc machine, install Splack 8.0, upgrade to Splack-current, and build a 2.4.27 or later kernel.

Sun4m SMP requires kernel 2.4.27 or later. Sun4d SMP requires 2.4.27 plus patches, the patches should be included in 2.4.28. Sun4d SMP will not work with serial console: install a framebuffer, monitor, and keyboard.

FIRE is a portable bootable cdrom based distribution with the goal of providing an immediate environment to perform forensic analysis, incident response, data recovery, virus scanning and vulnerability assessment.
Also provides necessary tools for live forensics/analysis on win32, sparc solaris and x86 linux hosts just by mounting the cdrom and using trusted static binaries available in /statbins.
Main features:
Forensics workstation/Data Recovery
- Instantly deploy a forensics workstation with tct, tctutils, mac-robber, and autopsy also provides perl 5.6.1 compiled with Large File Support.
Live System Incident Response
- Binaries are available for Incident Response on a live machine.
Virus Scanning
- Utilizing F-Prot 3.11beta http://www.f-prot.com you can scan for virii, worms, trojans, and all around harmful code.
- Just mount the filesystems that you want to scan and execute f-prot .
- Any filesystem you can mount, you can scan. mount and scan fat/ntfs/ext2/ext3/reiserfs partitions
- Scan your windows machines offline for virii that may not be detected with an "after the fact" anti-virus
- software installation.
Pen-Testing Platform
- I should NOT have to explain this portion: If the tools you would like to use are not in the distribution please make a request!

Software::Packager is a common software packaging interface.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager();
$packager->version(1.2.3.4.5.6);
$packager->package_name("Somename");
$packager->program_name(Software Packager);
$packager->description("This is the description.");
$packager->short_description("This is a short description.");
$packager->output_dir("/home/software/packages");
$packager->category("Applications");
$packager->architecture("sparc");

my %object_data = (
SOURCE => /source/file1,
TYPE => file,
DESTINATION => /usr/local/file1,
USER => joe,
GROUP => staff,
MODE => 0750,
);
$packager->add_item(%object_data);

my $version = $packager->version();
my $name = $packager->package_name();
my $program_name = $packager->program_name();
my $description = $packager->description();
my $description = $packager->short_description();
my $output_directory = $packager->output_dir();
my $category = $packager->category();
my $arch = $packager->architecture();

The Software Packager module is designed to provide a common interface for packaging software on any platform. This module does not do the packaging of the software but is merely a wraper around the various software packaging tools already provided with various operating systems.

This module provides the base API and sets default values common to the various software packaging methods.

Osalp is a project designed to implement a world class set of classes in C++ that will handle all of the audio functions one would like. It is designed to be multi-platform with UNIX based platforms as the base.

This project is still in the beta code phase and a beta version that will illustrate the power and flexibility is now available. This version supports the Linux (OSS) audio device, Solaris Sparc audio device, FreeBSD (OSS) audio device, wav, au, aiff, aifc, mp3, and numerousother formats.

It is important to note that this is not an application but a C++ library that others can use to create an audio application or to easly add audio capabilities to an existing application. OSALP was originally designed and developed by Bruce Forsberg out of need to manage and edit large sound files in a simple manner. Currently the project is being maintained by Darrick Servis.

The library is built on a set of core classes that provide the basic functionality. New classes to operate on data are derived from these classes. These classes provide a powerful chaining process. This allows one to build an audio chain much like one would build with building blocks. Audio data is encapsulated into a single class. This allows one to handle data conversions in one place.

There is a file base class (aflibFile) that defines the API for any device or file classes that are to be developed. They are implemented as dynamically loaded shared objects so that new file types can be added without recompiling the base library or needing to link them to an application. This will allow third parties to support their proprietary formats as a binary "plugable modules".

Linux & FreeBSD Device (OSS) -- aflibDevFile
Solaris Sparc Device -- aflibSolarisSparcDevFile
WAV (linear, mu-law, a-law) -- aflibWavFile
AU (linear, mu-law, a-law) -- aflibAuFile
AIFC -- aflibAifcFile
AIFF -- aflibAiffFile
MP3 using Lame encoder -- aflibLameFile
MP3 using Blade encoder -- aflibBladeFile
MP3 reader using splay library -- aflibMpgFile
MP3 reader using mpg123 executable -- aflibMpg123File
Sox library interface (supports most formats supported by the sox sound tools library -- aflibSoxFile

Currently there are several worker classes. These are the classes that actually do the work. These classes are not tied to any GUI but are GUI neutral. This allows developers to write code using the GUI of their choice.

Audio Sample Rate Converter -- aflibAudioSampleRateCvt
Audio Pitch Change -- aflibAudioPitch
Audio Test Source -- aflibAudioConstantSrc
Audio Editing -- aflibAudioEdit
Audio Timer Recording -- aflibAudioRecorder
Audio VU Meter and Spectrum Display -- aflibAudioSpectrum
Audio Mixing -- aflibAudioMixer
Butterworth Filter -- aflibAudioBWFilter
Reading Audio Data from Memory -- aflibAudioMemoryInput
Reading and Writing Audio Data to Devices or Files -- aflibAudioFile

There are also utility classes. These are not part of the main audio chain but are probably needed by most audio applications or are used indirectly by the worker classes.

FFT -- aflibFFT
User Environment Storage and Retrieval -- aflibEnvFile
Audio sample data -- aflibSampleData
Sample rate conversion -- aflibConverter